Hello Jeff,
First of all I apologize for my late reply. We had a couple of days off here.
When the updater determines that it needs to update the program, does it then copy itself to a Temp folder, and then the updater in the Temp folder is started and downloads the .msi file?
Yes, this is our default implementation.
One last note. I think the hanging updater.exe on my computer may have been caused by using the installation procedures for installing the updater.exe as a service for AI 10.2 after upgrading to AI 10.5.1. I noticed that the help files had some significant differences in how to install the updater.exe as a service when upgrading from AI 10.2 to 10.5.1, but there was no notification to me when I upgraded the project that I should fix anything. Ideally the newer version of AI could tell me that the process has changed and then ask me if I want it to fix it for me. At a minimum it would have been helpful if it notified me that something had changed, and that I needed to make some modifications.
Indeed, the configuration settings for
installing updater as a service have been changed in our last versions of Advanced Installer. We'll try to add a notification regarding this scenario in a future version of Advanced Installer, thank you for your suggestion.
After further testing, I found the problem was not selecting the "Delete update package file after installation" option in the Update project.
If the old msi file was not deleted, the updater would not overwrite the file and try to run the old msi file. I think that running the install for the same version that was installed was trying to bring up the dialog to repair/remove the install. Since the install was in silent mode and was run from a service (SYSTEM account) no dialogs show up on the screen, and would cause the updater.exe process to hang. The only way to then get it working again was to manually delete the old msi package and terminate the updater process.
I am guessing that the reason the msi did not get overwritten is because my program is installed as a service and the SYSTEM account was not given the proper privileges?? The problem will start to show up after the second update is made available.
Indeed, this is a possible scenario if you are using the same name for your updates items added in the "Updates" page of your updates configuration project. Please keep in mind that it is mandatory to use a unique name for each update item added in the
"Updates" page of your updates configuration project. The updater downloads the updates to the path specified in the "Updater page -> Downloads updates in this folder" field. Also, the MSI update package is downloaded (at the above path) to a sub-folder having the same name as the corresponding update item added in the "Updates" page of your updates configuration project.
Also, as another solution you can enable the "Delete update package file after installation" option for all of your updates file.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging