Update server just won't go away

[davedoc]

I'm having a hard time removing an update server from my list. I added a test server to my list and left the time out at the default of 30 seconds. My app now spends 30 sec spinning it's wheels trying to find this server because it's is not available.

So now I've removed the server from both the Project->TrueUpdate Servers list and from the FTP list in the tu2 file. I've verified that this is now removed by diff'ing the files. I then rebuild my client files appName.exe and appName.dat and include them in the latest installer.

After installing and rerunning my program I see in my logging that it is STILL looking for this server that I've removed.

Where else do I need to remove this server name from to get this to go away?

[Mark]

Hi davedoc,

I'm not sure what the problem could be as nothing like this has been reported before. Are you sure that you are including the correct files in your installer?

What happens if you simply re-build your TrueUpdate project and then run the resulting executable? Does it look for the incorrect server there?

In general all you need to do (unless you have hard-coded in the server downloads manually in the client script) to remove a TrueUpdate server is delete the server from the list under: Project | TrueUpdate Servers. Once it is removed from that list it should not have any effect on the runtime.

I ran a quick test and was able to confirm that removing the server from the server list removed it from the runtime.

[davedoc]

yup, even when I run it directly from the output folder it still looks for the old server :-/ I'm completely buffaloed what it might be.

[Mark]

Hi davedoc,

Perhaps you could email me your project file (mark@indigorose.com) so that I could take a look at it. In the email please let me know the address of the server that you do not want TrueUpdate to access. Then I will debug it and try to see what is happening.

I noticed in a previous post that you mentioned that you hard-coded in a few HTTP actions, are you sure that you have removed all of the hard-coded actions that may be accessing that incorrect server?

[davedoc]

emailed just now