MSI Package Condition Settings

To create a conditional statement that checks for the presence of a product that was installed by an .msi package with a particular product code, click the ellipsis button (...) in this setting to browse to the 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}.

Tip: You can use an asterisk as a placeholder for the current package’s product code, package code, and product version when you are defining eligibility and detection MSI package conditions, as long as the package that you are configuring is an .msi package.

To create a conditional statement that checks for the presence of a product with a particular product version that was installed by an .msi package, click the ellipsis button (...) in this setting to browse to the package and have InstallShield enter the product version for you. As an alternative, you can manually 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.

Tip: You can use an asterisk as a placeholder for the current package’s product code, package code, and product version when you are defining eligibility and detection MSI package conditions, as long as the package that you are configuring is an .msi package.