AUBackend Using Old (cached?) client.wyc File

I am evaluating wyUpdate and the Automatic Updater for my product and have created a Windows service that uses the automatic updater backend to update the application. Everything worked perfectly until I updated the download site in the client.wyc file (using wyBuild). For some reason, when the service starts the update (it appears to be when I call Initialize or AppLoaded) the client.wyc file in the folder where the service (and wyUpdate.exe) is running from reverts to an older version with the old download site.

Here are the steps I take:

- Changed the download site in wyBuild- Rebuilt wyUpdate- Built my service and deployed it with wyUpdate and client.wyc files- Opened the client.wyc file to verify the correct download site- Triggered the service to start checking for updates (using a custom command)- Update fails, open client.wyc and it is now pointing to our old download site (the file has an old creation date as well)

I attempted to clear the cache as mentioned in this post https://wyday.com/forum/t/682/wyupdate-seems-to-prevent-application-from-running-after-upd/, along with the appdata cache for the system profile (since the automatic updater is being called from a service) but it is still reverting to this old file.

We are wanting to purchase wyBuild for our product but don't want to move forward until we are sure that it will work for us. Thank you!

is running from reverts to an older version with the old download site.

It sounds like you have a client.wyc file in your updates (in your wyBuild project in the Files & Folders). Look at that file (double click it). Does it have the old download site?

Hi Sam, I checked my wyBuild project file (the .wyp file) and I don't have any client.wyc files listed in my files and folders. These are the cache locations that I cleared:

%appdata%\wyUpdate AU%userprofile%\wcC:\Windows\System32\config\systemprofile\AppData\Roaming\wyUpdate AU

Are there any other cache locations that I missed? I will try running the installer on a different box today to determine if it is something in the built project or something with my development machine.

I tried it on a different box and got another error that lead me to the solution. In my installer I was not including the AutomaticUpdater.dll file with my service. So when my service ran it must have found the AutomaticUpdater that was installed on my box. My guess is that the old client.wyc file was somehow cached in the installed AutomaticUpdater? As soon as I deployed the AutomaticUpdater.dll file with my product it began talking to the correct download server.

Thank you for your help!

The AutomaticUpdater never caches individual files. It caches updates only when it's in the middle of an update.

Make sure you're not including the client.wyc in your wyBuild project file (or, if you're changing the download site then *do* include the client.wyc in your project file -- wyUpdate isn't magic. It needs to know if you change anything.)

Also, make sure you actually build your updates and actually upload them to your servers.