Configuring Component Conditions

InstallShield 2015

Project: This information applies to the following project types:

Basic MSI
DIM
InstallScript MSI
Merge Module
MSI Database
MSM Database
Transform

Conditional installation of your components can be useful if you are creating different versions of the same product—for example, a trial version and a full version. You might not want to provide full functionality in the trial version, therefore you would not install all of the components. Another use for conditional component installation is to save disk space. If the target system does not have enough disk space for all of the components, you can set non-required components to install conditionally.

Using the component’s Condition setting, you can enter a statement that the installation must evaluate before setting up your component’s data on the target system. The component is not installed if its condition evaluates to false. However, the component is installed or advertised if its condition evaluates to true, assuming that its feature is selected for installation.

To set a condition for a component in your project:

1. In the View List under Organization, click Setup Design (for installation projects only) or Components.
2. Select the component that you want to configure.
3. Click the Condition setting and then click the ellipsis button (...). The Condition Builder dialog box opens.
4. Do one of the following:
In the Conditions box, type the component condition.
Use the Properties list, the Operators list, and the Add buttons to build your condition:
a. In the Properties list, select a property and then click the Add button. InstallShield adds the property to the Condition column.
b. If your conditional statement should contain an operator, select an operator in the Operators list and then click the Add button. InstallShield adds the operator to the conditional statement.
c. If your conditional statement should contain a value, enter the value.
5. Click OK.

Important: InstallShield performs basic condition validation; however, you should still double-check that your condition statements evaluate to the expected outcome. For more information and example conditions, see Building Conditional Statements.

See Also