Failed to Update

Try canceling the update and retrying. If that doesn't work, then clear out the cache folder by opening a cmd window and enter these 2 lines:

rmdir /s /q "%userprofile%\wc"rmdir /s /q "%appdata%\wyUpdate AU"

Once it updates do I need to replace the Automaticupdater.dll and AutomaticUpdater.xml files in my program files?

Thanks

Manually? No. You should, however, always build your app with the latest version of the AutomaticUpdater. When you release your next version of your app make sure it's built with the latest AutomaticUpdater.

Why we need to clear cache if we get the errorr. When we get this error?

We can't reproduce this error -- we never have. If you can tell us how, well be glad to make a proper workaround for this error.

Instead of clear this cache manually, this application should clear it automatically when error gets.

I got the error every time i run the application until I manually removed the files you said to remove from cache. Is there any other option to remove through the application.Because user cant do this everytime if he faces the same situation.

We can't reproduce this behavior. Tell us how to reproduce this error and we'll fix it.

Found out how to reproduce the Adler32 error. This happened when we decided to change a project name. Here is the steps we took to cause the error. Also a way to avoid the error.

Create an update as you normally would and check that it works as it should.

After we changed the namespaces and project name in Visual Studio, (you don't need to do anything in VS to reproduce the error) we created a new folder structure used for the new updates simply by copying the old update folder and renaming it to reflect the new project name. We did this for both the server files and the folder where we keep the versions, each version has its own folder. Folder structure is fairly simple and isn't the cause of the error. The point is, getting current users the ability to get the new update with the new project name.

We took the wyBuild project file, not the old one, but the copy of the old one we made when we copy/pasted the folders and used that project file to build on with the new version. Reason is, we needed to keep the previous versions as they were, add a new version, change the folders where the builds were saved, change the url where to download the updates and where the server files were uploaded too.

The old update is still live and when checked for an update, it returns no new update available. The new update is created and is live in a different folder than the old, except the current users don't see it when checking for updates. We have to over-write the old wyserver.wys file with the new one, so when the update is checked, it will say a new update available and also where to download the new updates. This is the key to avoiding the error, only copy over the wyserver.wys and nothing else. At first, we changed the update upload path to the old update folder, which did what we needed with the wyserver.wys file, but is also created new files in that folder. Not sure why this causes an issue, logically, wyserver.wys shouldn't care what else is in that folder because the updates are actually located on a different url, but for some reason it does and it doesn't like it (throws the Adler32 error).

The first attempt to fix the error, we changed the updates file naming to be more generic across the board, ie instead of the default, $collapse(%product%.%versionfrom%.to.%versionto%).wyu, we went with $collapse(update.%versionfrom%.to.%versionto%).wyu so each file would be called update instead of product name. This attempt didn't work because again, we overwrote all of the update files in the old update folder.

We aren't using signing. The server is a basic IIS with SSL.

If you need any further details, let me know.