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.

Select the product configuration that contains the release in the InstallShield project that you want to associate with the selected package.

When you start a build of a release for a Suite/Advanced UI project that includes one or more InstallShield project packages, InstallShield first builds the designated releases in the associated InstallShield projects, and includes them as packages in the Suite/Advanced UI installation that it generates.

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 Windows App 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 to mark this package as shared.

The shared package functionality helps to ensure that if two or more Advanced UI or Suite/Advanced UI installations are sharing a package, the package remains on the target system until all of the Advanced UI and Suite/Advanced UI products are removed.

If you select Yes for this setting, ensure that you also use the same package GUID in all Advanced UI and Suite/Advanced UI projects that are sharing the package.

To learn more, see Sharing Common Packages Among Different Advanced UI and Suite/Advanced UI Installations.

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

Specify a name for the log file. Do not include a path for the file; the Advanced UI or Suite/Advanced UI /log command-line parameter lets end users specify the directory for the package log files.

If you leave this setting blank, the name of the log file that the installation creates is PackageGUID.log, where PackageGUID is the GUID that is assigned to the package in the Package GUID setting in the Packages view.

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 command line that the Advanced UI or Suite/Advanced UI installation should pass to the .exe package to enable the logging. Include any appropriate supported flags. If the .exe package that you are configuring supports it, include a path that references the Advanced UI or Suite/Advanced UI property ISLogDir, enclosed within square brackets, in place of the path to the directory where the log file should be created.

For example, to generate a log file that logs everything verbosely for an .msi package that is run by a Setup.exe file that InstallShield built, enter the following command line:

/v"/l*v \"[ISLogDir]FileName.log\""

The Advanced UI or Suite/Advanced UI installation replaces [ISLogDir] with the path to the folder that will contain the log file. The Advanced UI or Suite/Advanced UI /log command-line parameter lets end users specify the path to the directory for the package log files.

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 determine whether the target system meets the requirements that are necessary for the package to be run. For example, if the package should be run only on 64-bit systems, you could set up an x64 platform requirement in a condition; the Advanced UI or Suite/Advanced UI installation would launch the package only on 64-bit systems. You may also want to set up an eligibility condition to prevent end users from being able to install the current package version over a future newer version.

To add one or more new eligibility conditions, click the New Condition button in this setting. InstallShield adds a new row under the Eligibility 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 Eligibility Condition setting says (Condition). If none are configured, the Eligibility 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 setting for .msi, .msp, .exe, and InstallScript packages. It is also under the Remove, Repair, and Modify settings for .exe packages.

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.

When you type a value for this setting, you can include one or more formatted expressions that contain property names, environment variable references, and other special strings; at run time, the installation expands the values of these expressions. To learn about the syntax that is available for these expressions, see Using Formatted Expressions that Advanced UI and Suite/Advanced UI Installations Resolve at Run Time.

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.

When you type a value for this setting, you can include one or more formatted expressions that contain property names, environment variable references, and other special strings; at run time, the installation expands the values of these expressions. To learn about the syntax that is available for these expressions, see Using Formatted Expressions that Advanced UI and Suite/Advanced UI Installations Resolve at Run Time.

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.

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.

When you type a value for this setting, you can include one or more formatted expressions that contain property names, environment variable references, and other special strings; at run time, the installation expands the values of these expressions. To learn about the syntax that is available for these expressions, see Using Formatted Expressions that Advanced UI and Suite/Advanced UI Installations Resolve at Run Time.

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.

When you type a value for this setting, you can include one or more formatted expressions that contain property names, environment variable references, and other special strings; at run time, the installation expands the values of these expressions. To learn about the syntax that is available for these expressions, see Using Formatted Expressions that Advanced UI and Suite/Advanced UI Installations Resolve at Run Time.

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:

For details on determining the best option to select, see Specifying the Behavior for an Advanced UI or Suite/Advanced UI Package that Requires a Restart.

Specify the name of the server where the Web Deploy package should be deployed.

You can leave the Suite/Advanced UI property that InstallShield assigns to this setting by default when you add the package to your project, or you can specify your own property (enclosed within square brackets). As an alternative, you can specify a hard-coded value.

For more information, see Adding a Web Deploy Package to a Suite/Advanced UI Project.

Specify the password for the user account that will be used to deploy the Web Deploy package.

You can leave the Suite/Advanced UI property that InstallShield assigns to this setting by default when you add the package to your project, or you can specify your own property (enclosed within square brackets). As an alternative, you can specify a hard-coded value.

For more information, see Adding a Web Deploy Package to a Suite/Advanced UI Project.

This setting lets you specify one or more run-time actions that the Suite/Advanced UI installation should launch before installing, removing, repairing, or modifying the package. The actions must already be added under the Actions explorer in the Events view.

To specify an action, click the Add Events button in this setting, and then click the action. InstallShield adds a new Action setting under the Package Configuring setting, and sets its value to the name of the action that you selected. Use the buttons in the Action setting to specify one or more conditions that the Suite/Advanced UI installation should use to evaluate whether the action should be launched.

This read-only setting shows the name of an action that is associated with the selected package and defined in the Events view. To define a condition that determines whether this action is run for this package, configure the subsettings under the Action setting as needed.

If you associate more than one action with the package, list the actions from top to bottom in chronological order, according to when they are launched at run time. To change the order of the actions, point to the Move Condition button in the setting of an action that you want to move, and the click the appropriate direction (Move Up or Move Down).