SparkleFlow is the acclaimed packaging solution that combines all aspects of a software packaging project into a single interface. Preparing an application migration? Need to reduce your TCO? Need to manage lots of applications? Want to setup your applications right now and not waste to much of your value time? SparkleFlow Package Management offers the complete solution for creating structure in your packaging project.
Written by Manfred van Poorten
Description:
ICE27 validates the sequence tables of an installation package for valid actions, action sequence restrictions, and organization in Search, Costing, Selection, and Execution sections.
The ICE27 custom action validates the following:
· That the actions listed in the Action column of the sequence tables are a standard actions, a custom action listed in the CustomAction table, or a dialog box listed in the Dialog table.
· That actions subject to sequencing restrictions are in the correct relative order to each other in the action sequence. Sequencing restrictions result when one action is dependent on another.
· That actions restricted to a particular section of the sequence are located where they belong. ICE27 validates the following organization of the sequence tables. Note that not every sequence table has every section. See the suggested sequence tables in Using a Sequence Table
ICE27 validates the following tables:
· AdvtExecuteSequence
· AdminUISequence
· AdminExecuteSequence
· InstallUISequence
· InstallExecuteSequence
Concerns:
ICE27 posts an error message if there are sequence tables in the package with invalid action sequencing or organization.
Additional Information:
Certain actions are related to each other. These are grouped in so-called ‘Sequence table sections’. The sections are displayed as follows:
|
Section: |
Reach: |
Actions located in this section: |
|
Search |
From start till CostInitialize |
Find actions (Files / application / registry). ‘AppSearch’ and ‘CCPSearch’ actions. |
|
Costing |
From CostInitialize till CostFinalize |
Everything related to FileCosting (Disc usage). ‘CostInitialize’, ‘FileCost’ and ‘CostFinalize’ actions. |
|
Selection |
From CostFinalize till InstallValidate |
Actions which set the ‘state’ for folders and features. SetODBCFolders action. |
|
Execution |
From InstallValidate till InstallFinalize |
All other script actions, from Registration, publication till installation. The ‘InstallFinalize’ action is only needed if there are indeed actions located in this ‘execution section’. |
|
PostExecution |
From InstallFinalize till the end |
For everything that needs to be done in retrospect. This is indeed the most acceptable place for nested MSI’s! RemoveExistingProducts action. |
Examples of possible errors:
You must resolve these errors. Keep in mind the following:
Error 1: The CustomAction 'ExecuteProgram1' is not located in the CustomAction Table. Include it in this location.
Error 2: ‘InstallFinalize’ must be included in the InstallExecuteSequence table.
Error 3: Place the ‘IsolateComponents’ action before the ‘CostFinalize’ action.
Error 4: Place the 'InstallFiles' action after the ‘MoveFile’ action.
» Back to article overview