Scheduling of Custom Actions |
Sequence tables are used to schedule "standard" as wellas custom actions that you define. The main (but possibly not only) tables you will use are (examples below):
Custom actions are generally executed in numeric order, you can use the GetSeqNumber() function to dynamically allocate unused numbers for you but all MAKEMSI commands that perform scheduling will automatically do this for you.
Sequence table Example |
This shows the "InstallExecuteSequence" table in "ORCA" ("Sequence column heading click to sort in order of execution):
InstallExecuteSequence - UISAMPLE.MSI Sequencing |
You will probably use this table more often than the "InstallUISequence" table. The default sequence of custom actions is:
InstallUISequence - UISAMPLE.MSI Sequencing |
Items in this table are not executed in a silent install. The default sequence of custom actions is:
Action | Sequence Number |
---|---|
FatalError | -3 |
UserExit | -2 |
ExitDialog | -1 |
LaunchConditions | 100 |
PrepareDlg | 140 |
FindRelatedProducts | 200 |
AppSearch | 400 |
CCPSearch | 500 |
RMCCPSearch | 600 |
CostInitialize | 800 |
FileCost | 900 |
CostFinalize | 1000 |
MigrateFeatureStates | 1200 |
WelcomeDlg | 1230 |
ResumeDlg | 1240 |
MaintenanceWelcomeDlg | 1250 |
ProgressDlg | 1280 |
ExecuteAction | 1300 |