What I'm trying to achieve is :
1) Having the updater check for updates, download them and install them BEFORE the application is run
2) Doing so with minimal user interaction. We want to force these updates onto the user
3) Avoid having the application forceably closed once the install starts. We don't want users to lose any work, etc. This point is quite important
I'm looking for suggestions on how to improve what I currently have or completely alternative solutions.
What I currently have is setup as a test is
1) Base installer for first time install (let's call it Version 4)
2) I've defined an update. In the Command Line, I entered /passive
3) Created a new version of my install package (let's call it Version 5)
4) In my application, the very first thing I do is run the updater with the command line of /silentall -nofreqcheck
So the result is:
* Initially install the app. Works fine
* Launch the app (version 4). I can see the icon in the system tray, as it downloads. Takes a while to download so there's a good possibility other users will start using our app
* When the download is complete, the install launches. The users gets the UAC message (undesirable - as it's possible the user will say No - but not a big deal). The installer then forceably closes the app
* Upon re-launching my app, I can see I'm upto Version 5
I'm aware I can add a custom action to detect or stop the process. Two problems I see are:
1) With the stop process, it forceably closes it. I'd rather we ask the user to shut it down before proceeding, similar to the MsiRMFilesInUse dialog. Is that possible?
2) Since I'm running with /passive, appears I can't ask the user anything before installing.
Any suggestions?
FOLLOW US
Get the latest news in Application Packaging