ICE75 verifies that all Custom Action Type 17 (DLL), Custom Action Type 18 (EXE), Custom Action type 21 (JScript), and Custom Action Type 22 (VBScript) custom actions are sequenced after the CostFinalize action. These types of custom action use an installed file as their source. ICE75 checks the InstallUISequence Table, InstallExecuteSequence Table, AdminUISequence Table, and AdminExecuteSequence Table. Note that the CostFinalize action is required in these sequence tables.
Result
ICE75 posts an error if it finds a custom action using an installed file as a source file that is not sequenced after the CostFinalize action.
Example
ICE75 reports the following errors for the example shown:
CostFinalize is missing from 'AdminUISequence'. CA_FileExe is a custom
action whose source is an installed file. It must be sequenced after
the CostFinalize action.
CA_FileDLL is a custom action whose source is an installed file. It
must be sequenced after the CostFinalize action in the
AdminExecuteSequence table
CustomAction Table (partial)
Action | Type | Source |
---|---|---|
CA_FileExe | 18 | FileExe |
CA_FileDLL | 17 | FileDLL |
AdminUISequence Table (partial)
Action | Sequence |
---|---|
CA_FileExe | 1100 |
AdminExecuteSequence Table (partial)
Action | Sequence |
---|---|
CA_FileDLL | 800 |
CostFinalize | 1000 |
To fix the errors, sequence the custom actions after the CostFinalize action.
See Also
Send comments about this topic to Microsoft
Build date: 8/13/2009
© 2009 Microsoft Corporation. All rights reserved.