Environment: The full installer installs the support service and patches for the application are set to be installed without elevation. They have also been marked as patch and not a full package.
Observation: When the patch is installed via the Updater whether it is with UI or not, there will be a force reboot without prompt if any resources are locked during the time of installation. E.g. if the program is still open.
Question 1: How do we remedy this situation? Ideally, if resources are locked at that point in time there should be a prompt to ask to reboot rather than a force reboot. Is this because of the install without elevation checkbox? Do I have any alternatives if we still want the updates to be installed without human interaction?
Question 2: Is there any way to set the updater such that only my application is able to trigger it? Currently it is being triggered by command line but the updater can be double clicked and launched by the user. This is related to question 1 as the application can guarantee that it is closed before starting the update process but not if it is user triggered. Our expected work flow expects users to update via our app not via the updater exe.
Note: Currently unable to use the Auto Close Applications function in the updates project because the application already has a use for the WM_CLOSE message. It is possible for us to make changes to our application but we would like to explore other alternatives first being going down that road.
Thanks!
FOLLOW US
Get the latest news in Application Packaging