Thanks, Daniel. I want to install another MSI project from my installer when I doing a "Complete installation" of the project. When I select the "Typical installation", I want to ignore install MSI. I create Chained prerequisites with condition to install: (NOT Installed OR OLDPRODUCTS) AND ...
The documentation says that "Preserve Install Type of the old version" requires administrative privileges. It follows that if I run the update with limited rights, the update can not be quiet (with /qr or /qn keys)?
When I manually updating the program is installed as per-user.
When I run with /qr - program is installed as per-machine with path as per-user.
I set "Preserve Install Type of the old version" as recommended above.
When I do a manual update of the program, the program is updated normally. When I do a silent update of the program with the key /qr or /qn, it creates another copy of the program, which is stored in this way, as the previous version.
Thanks, Eusebiu. It worked. Now I want to go back to the first question. I am creating an application with the installation type "Per-machine if user is administrator, per-user otherwise". If I run a program with limited rights the installer set per-user and the program is installed. When I launch ...
I understood. I create temporary files before deleting previous versions of the temporary files are created, but when a new version is installed, the temporary files are missing (temporary files are not created during the upgrade). And custom action not executed.
Thanks. Everything works correctly.
I've got one more question.
I need to start the custom action "Launch file", when the program is updated from a previous version. I add OLDPRODUCTS condition , but the custom action is not executed.
whats wrong?
Why, when I install the program, then I install per-user (install path C:\Users\user\AppData\Local\Programs\My app).
But when I run the update (Setup.exe /qr ), it is always set per-machine (C:\Program Files (x86)\My app)?
I set up the installer and choose the installer mode (per-machine or per-user).
For manual update installer correctly selects the initial setup mode (read from registry from the vbs-script).
If auto-update setting mode is always selected for the per-machine.
Please help me. I need to install a third-party MSI from my installer after the installation of all components.
When I delete my installer - a third-party installer must be uninstalled.
How to implement this?
I need to display a message that another version of the installer is installed and the installer must stop the installation.
The old installer and new installer have a different ProductCode.
It is necessary to define that other installer is installed and display a message.
FOLLOW US
Get the latest news in Application Packaging