The logical value of a property that has been set is True. To determine whether a property is set without actually getting its value, test the logical expression "MyProperty" or "Not MyProperty". When the property MyProperty is set, the former evaluates as True and the latter as False.

One or more properties can be combined with operators to form logical expressions used in a conditional statements. For more information about the operators that can be used in conditional statements, see Conditional Statement Syntax.

A conditional statement using properties can be entered into the Condition column of the Condition table to modify the selection state of any entry in the Feature table.

Conditional statements with one or more properties are commonly used in the Condition column of database tables.

The following tables each have a column for conditional expressions:

• Condition table
• ControlEvent table
• LaunchCondition table
• InstallUISequence table
• InstallExecuteSequence table
• ControlCondition table
• AdminExecuteSequence table
• AdvtExecuteSequence table
• AdminUISequence table

Note that the six action sequence tables have fields for a condition. If the conditional expression in this field evaluates to False, the installer skips that action.

If you set a private property in the UI sequence by authoring a custom action in one of the user interface sequence tables, that property is not set in the execution sequence. To set the property in the execution sequence you must also put a custom action in an execution sequence table. Alternatively, you can make the property a public property and include it in the SecureCustomProperties property.

For more information, see Using a Sequence Table or Using Properties.

Send comments about this topic to Microsoft

Build date: 8/13/2009