I'm wondering what the schema is to setup a script that if a user accepts to install an upgrade on their PC, it checks to verify that the current version of the software is not running, then install. But if the current version is running, it prompts the user to save what they're working on and close the application, then when the application is, then, closed, it continues to install the upgrade. Or it forces the application to save the current file(s), that are open, then shut down the application, then run the upgrade.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
what I normally do is ask the user to install and in the message window tell them to save the work and close the program, and in the script I do a "taskill /F /IM program.exe" to make sure it's shutdown before upgrading it

if the user don't click anything then it's set to not install
Answered 01/24/2012 by: rmeyer
Second Degree Blue Belt

Please log in to comment
0
What you're asking for forces the application to save the current file(s), that are open, then shut down the application, then run the upgrade would be largely dependant on the software title.

As for the general behavior; I'd use a smart label to target the systems in need, then use a script of some type (K-Script, VB, Batch- whatever you are comfortable writing) to determine if it's running, then ask them to close it if it is, then ask again if it's still running (Looping about 5 times) and ultimately kill it if the user failed to read the bloody box 5 times. Or install while the software is not in use; again based on an installer script or a smart label.
Answered 01/26/2012 by: cblake
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity