Creating Nested Installation Custom Actions
InstallShield 2020
Project:This information applies to the following project types:
Important:Nested installations is a deprecated feature of the Windows Installer. Applications installed with nested installations sometimes fail because they are difficult for end users to service correctly. Microsoft Corporation recommends that you avoid using nested installations and nested-installation custom actions to install products that are intended to be released to the public. To learn more, see Concurrent Installations in the Windows Installer Help Library.
To create a nested installation custom action using the wizard:
|
1.
|
In the View List under Behavior and Logic, click Custom Actions and Sequences. |
|
2.
|
Right-click the Custom Actions explorer and click Custom Action Wizard. The Custom Action Wizard opens. |
|
3.
|
On Basic Information panel, specify a name and comment for your custom action and click Next. |
|
4.
|
On the Action Type panel, in the Type list, select Launch another .msi package. In the Location list, select Included within your main setup. |
|
5.
|
On the Action Parameters panel, browse for the location of the .msi file that you are launching. (For simplicity, assume that the child product is packaged with all files compressed into the .msi package.) The Target box enables you to specify command-line switches to pass to the child installation. For example, to install all of the features of the child installation with their default settings, and to use the same value for the ALLUSERS property used by the parent installation, type the following in the Target box: |
ARPSYSTEMCOMPONENT=1 ADDDEFAULT=ALL ALLUSERS=[ALLUSERS]
You can use similar expressions to use the same value of INSTALLDIR in the child as in the parent.
|
6.
|
Accept the default options on the Additional Options panel and click Next until you finish the wizard. |