Automatic Updater Cache

Dear Sam,

I'm using Automatic Updater now for 1 month and very glad with the results, it seems like its going to be a really good and simple way to keep my software updated for the users.

My main goal is to be able to use only the AutomaticUpdater dll without showing any additional UI for the users.

1. Is it possible to luanch automaticUpdater.InstallNow() and wyUpdater.exe will be launched silently, without showing the UI for the users? e.g. loading it minimized?

2. I'm still having a major issue with the caching mechanism, I'm using automaticupdaterWPF.dll version: 2.6.3.0. Sometime the updater thinks he has an update when its actually uptodate or he thinks the update is from lower version altough I have some updated version, e.g. trying to update from version 0.1 to 0.4 when I'm actually on version 0.3 and the update needs to be from 0.3 to 0.4.

Trying to reproduce this problem I found that when I delete the file located at:%appdata%\WyUpdate AU\ things are beeing resolved and on the next run I get the correct update status.

I don't need to mention that If the user continues and I run au.installnow() I get crashes and errors.

Nevertheless when I luanch wyUpdater.exe manually he knows how to override this information and always shows the correct update status. Is it possible to use the logic performed at wyUpdater.exe inorder to detemine to correct update status to the AU.dll ? or a way to delete caching file automatically before checking for new update? 😮 😮

Many thanks!Jan.

Hey Jan,

1. Is it possible to luanch automaticUpdater.InstallNow() and wyUpdater.exe will be launched silently, without showing the UI for the users? e.g. loading it minimized?

No. This isn't possible for a number of reasons. UAC prompt, in case processes are opened that need to be closed, if files are in use and need to be closed, etc. In other words, it's imperative the user be shown the updater while it processes the update.

Trust me, if we could make the updater completely invisible and make the update take 0 seconds to process, we would. Maybe in 20 years when computer technology is up to snuff.

2. I'm still having a major issue with the caching mechanism, I'm using automaticupdaterWPF.dll version: 2.6.3.0. Sometime the updater thinks he has an update when its actually uptodate or he thinks the update is from lower version altough I have some updated version, e.g. trying to update from version 0.1 to 0.4 when I'm actually on version 0.3 and the update needs to be from 0.3 to 0.4.

Stop running wyUpdate.exe in standalone mode. Either use the AutomaticUpdater completely or use wyUpdate.exe in standalone mode completely. Don't use a little of one and a little of the other. The reason the AutomaticUPdater is reporting new updates available after you've updated using wyUpdate.exe in standalone mode is that the AutomaticUpdater keeps the state cached. It doesn't know you used wyUpdate.exe (and why should it?).

Regarding problems with the AutomaticUpdater: we've fixed some major bugs in v2.6.6 (out now). If you find any other bugs, errors, or crashes report them and we'll fix them.

To sum up: stop telling your users to run wyUpdate.exe in standalone mode.

Reply
Discard post