Sequencing Custom Actions that Set Properties or Directory Properties

InstallShield 2015

Project: This information applies to the following project types:

Basic MSI
InstallScript MSI
Merge Module
MSI Database
MSM Database

When you are sequencing a custom action that sets a property or directory, the primary guideline that you need to follow is to make sure that the custom action runs before that directory or property is needed. For example, if you want to launch an executable file that is present on the target machine, the installation will probably need to search for it first.

Once the installation finds the executable file, its path can be added to the Directory table, and the executable file can be launched. However, if you call the custom action after you launch the executable file, the executable file will not be found.

Some other sequencing and scheduling restrictions include:

Validation rule ICE12 requires any type-35 custom action (called Set a directory in the Custom Action Wizard) to be sequenced after the standard CostFinalize action in the sequences.
Similarly, ICE12 requires any type-51 custom action (called Set a property in the Custom Action Wizard) that sets the value of a property found in the Directory table to be scheduled before the standard CostFinalize action.
Any custom action that sets a property should be scheduled for immediate execution.