Summary
This article discusses how to perform a major upgrade with a Basic MSI project when the previous releases used InstallScript MSI projects.Synopsis
This article discusses how to perform a major upgrade with a Basic MSI project when the previous releases used InstallScript MSI projects.
Discussion
If a major upgrade item is used in a Basic MSI to upgrade an old release that was InstallScript MSI, the Add/Remove Programs entry and any resources installed by InstallScript will be left on the machine. Normally, when an InstallScript MSI upgrades a previous InstallScript MSI, special code in the InstallScript engine runs to clean up these resources. However, if a Basic MSI is used to perform the upgrade, this code is not run and therefore the resources will be left on the machine. However, it is possible to perform a manual major upgrade using an EXE type custom action.
- Add a major upgrade item in the Upgrades view that references the old installation's Upgrade Code.
- On the Advanced tab on the major upgrade item settings, set the Detect Only setting to Yes. Make a note of the Detect Property name.
- Add a new EXE->Path referencing a directory action in the Custom Actions view. Name the custom action as needed.
- In the Working Directory field in the custom action, select TempFolder or SystemFolder from the drop-down box.
- In the Filename and Command line field, add one of the following command lines based on which version of InstallShield the InstallScript MSI project was built with:
InstallShield 12 and newer:
"[ProgramFilesFolder]InstallShield Installation Information\{Old ProductCode}\setup.exe" /uninst
InstallShield 11.5 and older:
"[CommonFilesFolder]InstallShield\Driver\<IS Version>\Intel 32\idriver.exe" /M{Old ProductCode} /uninst - Sequence the custom action at any point after CostFinalize in the Install UI Sequence.
- In the Install UI Condition field, enter a condition such as the following (using the Detect Property as noted in step 2 above):
Not Installed AND DETECT_PROPERTY_NAME - Build and test the project.
Additional Information
More information on upgrades can be found in the help library article Major Upgrades.
Related Articles
Windows Installer Property PATCH - Working With Conditions in a Basic MSI Specific to a Patch Install 3Number of Views Variable SETUPEXEDIR returns blank when running a Patch Update 3Number of Views InstallScript MSI Major Upgrade Results in "Setup Launcher Unicode Has Stopped Working" 10Number of Views An Error 1601 or 1719 May Occur After Installing the MSI 3.1 Engine with InstallScript MSI Projects 3Number of Views Warning-7065 Windows Installer 3.1 Engine could not be found, while creating a patch and "Error reading setup initializati… 11Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago