Downloading and Installing updates prior to application launch

I have been evaluating wyBuild as an update solution for several of our internal applications. We currently have batch files that check date stamps as "launchers" and I would like to get away from that. I am using the .NET4 AutomaticUpdate extension for WPF currently.

It has been mentioned several times about "forcing" an update to the application. What I am wondering, is there a way on every application launch, to check for new updates (set the DaysBetweenChecks to 0), but force an install prior to application launch if an update exists even if it isn't downloaded yet. I understand that this is not the best user experience, but it is critical that the business have the most up to date version.

I have seen the responses for a dummy service and I have toyed with the idea of adding a scheduled task, but I would really like to see the application handle all the work. Is this what the proposed "critical" flag will be implemented for?

We currently have batch files that check date stamps as "launchers" and I would like to get away from that. I am using the .NET4 AutomaticUpdate extension for WPF currently.

I'm not quite sure what this means. Are you using this with wyUpdate? And what does this accomplish? Or are you saying you used this before using wyupdate?

It has been mentioned several times about "forcing" an update to the application. What I am wondering, is there a way on every application launch, to check for new updates (set the DaysBetweenChecks to 0), but force an install prior to application launch if an update exists even if it isn't downloaded yet. I understand that this is not the best user experience, but it is critical that the business have the most up to date version.

The AutomaticUpdater is meant for asynchronous updates -- that is, updates that are downloaded, extracted, and then installed at the end-user's convenience. The best way to "force" an update is to use wyUpdate in "standalone" mode.

Reply
Discard post