Open topic with navigation

AddCondition Method (Advanced UI and Suite/Advanced UI)

InstallShield 2015 » Automation Interface » Advanced UI and Suite/Advanced UI

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.

The AddCondition method adds a condition to a condition group.

To add an extension condition to a condition group, use the AddExtensionCondition method.

Syntax

AddCondition (ConditionCheckName As String) As ISWiSuiteCondition

Parameters

AddCondition Method Parameters

Parameter

Description

ConditionCheckName

Specify the name of the type of condition check. Available options are:

• Platform—Check target systems for one or more characteristics such as the operating system version, the architecture, and other platform details on target systems.
• FileExists—Check target systems for the presence of a particular file.
• FileValue—Check target systems for specific information—date, version number, or content—for a particular file.
• RegistryExists—Check target systems for the presence of a particular registry key, and optionally a specific value name.
• RegistryValue—Check target systems for specific information—DWORD, QWORD, string, multistring, file version, or product version—for a particular registry entry. If you do not specify a value name, the default value for the key that you specify is used for the comparison.
• PropertyValue—Check the value of a particular built-in Advanced UI or Suite/Advanced UI property, or a property that is defined in the Property Manager view.
• MsiInstalled—Check target systems for the presence of a product that was installed by a particular .msi package.
• MsiRelated—Check target systems for the presence of a version of a product that you want to update, or for the presence of future versions of a product that you do not want to downgrade. In either case, the product whose presence is being checked is installed by an .msi package.

ConditionCheckName (cont.)
• ParcelRef—Check whether a different package or a feature in the Advanced UI or Suite/Advanced UI installation is eligible for installation on a target system. For example, if a patch package is eligible for installation only if the base package is eligible for installation, you can create an Eligible Package condition to tie the patch’s eligibility to the base package’s eligibility.
• IspInstalled—Check target systems for the presence of a product that was installed by a particular InstallScript package.
• Locale—Match one or more locale-related settings on target systems.
• SuiteInstalled—Check whether a particular version of an Advanced UI or Suite/Advanced UI installation is already installed on a target system.
• AppxInstalled—Check target systems for the presence of a particular AppX app.
• ParcelAction—Check the target state of a particular package in the Suite/Advanced UI installation. This type of condition is available only for actions that are associated with an event in the Events view or Packages view.
• FeatureAction—Check the target state of a particular feature in the Suite/Advanced UI installation. This type of condition is available only for actions that are associated with an event in the Events view or Packages view.

Project: The ParcelAction and FeatureAction type of conditions are available in Suite/Advanced UI projects.

Applies To

• ISWiSuiteCondition

See Also

Building Conditional Statements in Advanced UI and Suite/Advanced UI Projects

Types of Condition Checks in Advanced UI and Suite/Advanced UI Projects

Creating a Custom Condition for an Advanced UI or Suite/Advanced UI Installation

InstallShield 2015 Help Library

June 2015

 Copyright Information | Contact Us