AutomaticUpdater behaving differently from Updater.exe

As suggested by you earlier, I have started separating my test updates from my production updates. To that effect I have defined separated build projects and separate Upload/Download Sites. If i put a "test" client file and a "test" updater in a new directory and start the updater.exe, it behaves as expected ("using latest version"). If, however, I start my app (in the same directory) that calls the automatic updater it comes back and wants to download the latest *production* release, and I am pretty sure neither client nor updater refers to that site. Does the automatic updater have some cache somewhere where it stores the results of its last download check? Or what else might be causing this behaviour?

Thx,bluewater

Don't switch back and forth between wyUpdate.exe as a standalone updater and the AutomaticUpdater. Use one or the other. The AutomaticUpdater caches some files at different times for different reasons. wyUpdate.exe as a standalone updater neither knows nor cares about the cached files, and thus doesn't touch them.

So always use the AutomaticUpdater.

I have now discovered that the .ForceCheckForUpdate method accepts a parameter 'recheck' to ignore cached updates. I have set this param to true and all is well.

thx