Common Tab

Enter a GUID that uniquely identifies this package. To have InstallShield generate a different GUID for you, click the Generate a new GUID button ({...}) in this setting.

Specify where the package should be located. Available options are:

If the Advanced UI or Suite/Advanced UI installation will be run uncompressed from fixed media—such as CD, DVD, or local network—use this option.

If the entire Advanced UI or Suite/Advanced UI installation must be self-contained in Setup.exe, select this option. Note that the Download From The Web option results in smaller installations and shorter download time; however, the Extract From Setup.exe option provides for a completely self-contained installation.

This option is recommended if your installation will be downloaded from the Internet and you want to minimize the Advanced UI or Suite/Advanced UI package size and download time. An Advanced UI or Suite/Advanced UI package is not downloaded if the correct version is already present on the target system.

Note that the option that you select in the Location setting may be overridden in the Releases view.

Project: In Suite/Advanced UI projects, this setting is available for edit. In Advanced UI projects, this setting is read-only, since an Advanced UI project has support for only one primary package.

In a Suite/Advanced UI project: Select the type of package that identifies whether the presence of this package on the target system should influence whether the Suite/Advanced UI installation runs in first-time-installation mode or maintenance mode.

Available options for this setting are:

At run time, if all of the primary packages in the installation are absent from the target system, the installation runs as a first-time installation. If any of the primary packages are present on the target system, the installation runs in maintenance mode.

For more information, see Primary Packages vs. Dependency Packages in Advanced UI and Suite/Advanced UI Projects.

The versions of Windows that support .appx packages do not install a sideloading package unless they trust the source of the package. If you are using a custom certificate, such as the one that is generated in Visual Studio, the Suite/Advanced UI installation can make Windows trust the source of your package by adding the custom certificate to the certificate store of target systems. The Suite/Advanced UI installation does this if you include the .cer file in your sideloading package, and specify it here.

Indicate the appropriate behavior that should occur when an earlier version of the package is present on the target system. Available options are:

Specify whether you want the package to generate a log file if the Advanced UI or Suite/Advanced UI installation is launched from the command line with the /log command-line parameter. Note that if a package does not have support for logging, it is recommended that you do not enable logging support for that package.

If you select Yes, configure each subsetting under this setting as needed.

For more information, see Supporting the Creation of Package Log Files for Command-Line Launching of an Advanced UI or Suite/Advanced UI Installation.

This setting is enabled if Yes is selected for the Enable Logging Support setting.

Specify the Windows Installer log /L flags that you want the package to use when generating the log file. For example, to generate a log file that logs everything verbosely, enter the following in this setting:

*v

For additional valid flags, see the /L description.

If you leave this setting blank, the asterisk (*) and v flags are used to generate the log file.

For more information, see Supporting the Creation of Package Log Files for Command-Line Launching of an Advanced UI or Suite/Advanced UI Installation.

This setting lets you specify one or more conditions that the Advanced UI or Suite/Advanced UI installation should use to evaluate whether the package is already installed on target systems. For example, if the package installs a specific file or registry entry, you can create a condition that specifies the file or registry key that the installation should search for.

To add one or more new detection conditions, click the New Condition Group button in this setting. InstallShield adds a new row under the Detection Condition setting. Select the appropriate option—All, Any, or None—from the list in this row. Then in this row, click the New Condition button, and select the appropriate option to continue building the conditional statement.

For more information, see Building Conditional Statements in Advanced UI and Suite/Advanced UI Projects.

If one or more conditional statements are configured, the Detection Condition setting says (Condition). If none are configured, the Detection Condition setting says (Empty).

If the Advanced UI or Suite/Advanced UI installation runs in first-time installation mode, specify whether you want this package to be launched as a first-time installation. The install operation is applicable if the target system meets the package's eligibility conditions and if this package's product is not already installed.

If you select Yes for this setting, configure the subsettings under this setting as needed. If you select No, the subsettings under this setting are disabled.

If the Advanced UI or Suite/Advanced UI installation runs in repair mode, specify whether you want this package to be launched in repair mode to repair the product that is installed by this package. The repair operation is applicable if the target system meets the package's eligibility conditions and if this package's product is installed.

If you select Yes for this setting, configure the subsettings under this setting as needed. If you select No, the subsettings under this setting are disabled.

This setting is a subsetting under the Install, Remove, Repair, and Modify settings.

Select the file in the package—the .msi file, the .msp file, or the executable file setup launcher—that the Advanced UI or Suite/Advanced UI installation should invoke.

This setting is a subsetting under the Install, Remove, Repair, and Modify settings.

If applicable, specify the command line that should be used to launch the target file (that is, the file that is selected in the Target setting) whenever the Advanced UI or Suite/Advanced UI installation is running with a user interface. Do not include the name of the file in this setting.

If you are configuring the Install and Remove operations for an .msi package, the only type of command-line parameters that you should enter are Windows Installer properties. If you are configuring the Repair and Modify operations for an .msi package, the only type of command-line parameters that you should enter are Windows Installer feature properties.

To enter a Windows Installer property, use the following format:

MYPROPERTYNAME=MyPropertyValue

Note that an Advanced UI or Suite/Advanced UI installation always launches .msi packages silently. Therefore, it is not necessary to pass a command-line parameter that hides the user interface of the .msi package.

For more information, including valid types of entries for this setting, see Passing Command-Line Parameters to a Package in an Advanced UI or Suite/Advanced UI Installation.

This setting is a subsetting under the Install, Remove, Repair, and Modify settings.

If applicable, specify the command line that should be used to launch the InstallScript package that is associated with the selected target file (that is, the data1.hdr file that is selected in the Target setting) whenever the Advanced UI or Suite/Advanced UI installation is running with a user interface. Do not include the name of the file in this setting.

If you are configuring the Install and Modify operations for an InstallScript package, you can use the Advanced UI or Suite/Advanced UI properties ISFeatureInstall and ISFeatureRemove in your command line. Set these properties to a comma-delimited list of feature names as follows:

ISFeatureInstall=Feature1,Feature2 ISFeatureRemove=Feature3

In the above example, Feature1 and Feature2 are selected to be installed; Feature3 is selected to be removed, if it is present.

Note that an Advanced UI or Suite/Advanced UI installation launches InstallScript packages silently by default. Therefore, it is not necessary to pass a command-line parameter that hides the user interface of the InstallScript package.

For more information, including valid types of entries for this setting, see Passing Command-Line Parameters to a Package in an Advanced UI or Suite/Advanced UI Installation.

This setting is a subsetting under the Install, Remove, Repair, and Modify settings.

If applicable, specify the command line that should be used to launch the target file (that is, the file that is selected in the Target setting) whenever the Advanced UI or Suite/Advanced UI installation is running silently (that is, without a user interface). Do not include the name of the file in this setting.

To update all of the features through an .msp package, you would enter command-line properties such as the following:

REINSTALLMODE=vomus REINSTALL=ALL

To update only certain features that are included in the .msp package, you would set REINSTALL to a comma-separated list of features that you want to be updated:

REINSTALLMODE=vomus REINSTALL=Feature1,Feature3,Feature5

Note that an Advanced UI or Suite/Advanced UI installation always launches .msp packages silently. Therefore, it is not necessary to pass a command-line parameter that hides the user interface of the .msp package.

For more information, including valid types of entries for this setting, see Passing Command-Line Parameters to a Package in an Advanced UI or Suite/Advanced UI Installation.

If applicable, specify the command line that should be used to launch the InstallScript package that is associated with the selected target file (that is, the data1.hdr file that is selected in the Target setting) whenever the Advanced UI or Suite/Advanced UI installation is running silently (that is, without a user interface). Do not include the name of the file in this setting.

If you are configuring the Install and Modify operations for an InstallScript package, you can use the Advanced UI or Suite/Advanced UI properties ISFeatureInstall and ISFeatureRemove in your command line. Set these properties to a comma-delimited list of feature names as follows:

ISFeatureInstall=Feature1,Feature2 ISFeatureRemove=Feature3

In the above example, Feature1 and Feature2 are selected to be installed; Feature3 is selected to be removed, if it is present.

Note that an Advanced UI or Suite/Advanced UI installation launches InstallScript packages silently by default. Therefore, it is not necessary to pass a command-line parameter that hides the user interface of the InstallScript package.

For more information, including valid types of entries for this setting, see Passing Command-Line Parameters to a Package in an Advanced UI or Suite/Advanced UI Installation.

This setting is a subsetting under the Install, Remove, Repair, and Modify settings.

The installation of an Advanced UI or Suite/Advanced UI package may require that the target system be restarted, as described in Restarting a Target System for an Advanced UI or Suite/Advanced UI Package.

Specify the behavior that should occur if the package requires that a target system be restarted. Available options are:

This setting is a subsetting under the Install, Remove, Repair, and Modify settings.

If the selected package requires that the target system be restarted after the product is installed, type the return code in this setting.

If multiple return codes exist, list each one separated by a comma.

If you do not know the return codes for the file that you are launching as the Advanced UI or Suite/Advanced UI package, contact the author of the package.

For more information on Advanced UI or Suite/Advanced UI packages that require a restart, see Restarting a Target System for an Advanced UI or Suite/Advanced UI Package.