InstallShield 2016
Project • This information applies to the following project types:
| • | Advanced UI |
| • | Suite/Advanced UI |
Edition • The Advanced UI project type is available in the Professional edition of InstallShield. The Suite/Advanced UI project type is available in the Premier edition of InstallShield. For information about the differences between these two project types, see Advanced UI Projects vs. Suite/Advanced UI Projects.
When you are building a conditional statement for an exit, detection, eligibility, or feature condition in an Advanced UI or Suite/Advanced UI project, or for an action condition in a Suite/Advanced UI project, you can create an InstallScript Package condition.
The InstallScript Package setting shows the condition that is configured for checking target systems for the presence of a product that was installed by a particular InstallScript package. To define this type of condition, configure the subsettings under the InstallScript Package setting as needed.
The following subsettings are available for this condition.
|
Setting |
Description |
||||||
|
Product Code |
To create a conditional statement that checks for the presence of a product that was installed by a particular InstallScript package with a particular product code, click the ellipsis button (...) in this setting to browse to the data1.hdr file of the uncompressed InstallScript package and have InstallShield enter the product code for you. As an alternative, you can manually enter the product code. A sample entry is {5D607F6A-AF48-4003-AFA8-69E019A4496F}. |
||||||
|
Product Version |
To create a conditional statement that checks for the presence of a product with a particular product version that was installed by an InstallScript package, enter the product version. Then use the Comparison setting to specify whether you want the product version to be less than, greater than, or equal to the value that you are specifying. The typical format for the version number is aaa.bbb.ccccc or aaa.bbb.ccccc.ddddd, where aaa represents the major version number, bbb represents the minor version number, ccccc represents the build number, and ddddd represents the revision number. The maximum value for the aaa and bbb portions is 255. The maximum value for ccccc and ddddd is 65,535. Note that although you can include the fourth field (ddddd) when you specify the product version, the Advanced UI or Suite/Advanced UI installation does not use this part of the product version to distinguish between different product versions. |
||||||
|
Verify Log Exists |
Select the option that describes whether you want the Advanced UI or Suite/Advanced UI installation to verify that the uninstallation log file that is registered for the product is present on target systems. If you leave this setting blank, the Advanced UI or Suite/Advanced UI installation behaves as if you selected Yes in this setting. |
||||||
|
Check Per-User Registration |
Select the option that describes whether you want the Advanced UI or Suite/Advanced UI installation to check HKEY_CURRENT_USER for uninstallation information on target systems. Available options are:
If you leave this setting blank, the Advanced UI or Suite/Advanced UI installation behaves as if you selected Yes in this setting. |
||||||
|
Comparison |
If you specify a version number in the Product Version setting, select the appropriate option to indicate how you want to compare the version number on the target system with the one that you enter. For example, if you want the condition to be true if the version on the target system is less than or equal to 4.0.0, enter 4.0.0 in the Product Version setting, and select Less Than or Equal To in the Comparison setting. |
See Also
Types of Condition Checks in Advanced UI and Suite/Advanced UI Projects
Guidelines for Defining Conditions in an Advanced UI or Suite/Advanced UI Project
Building Conditional Statements in Advanced UI and Suite/Advanced UI Projects
InstallShield 2016 Help LibraryAugust 2016 |
Copyright Information | Flexera Software |