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: 1. Between InstallValidate and InstallInitialize 2. Immediately after InstallInitialize, or after InstallInitialize if the actions between InstallInitialize and RemoveExistingProducts do not generate any script actions. 3. Immediately after InstallExecute or InstallExecuteAgain and before InstallFinalize (the same restriction as above applies). 4. After InstallFinalize.. Concerns: Additional information: It is preferrable to always use option 4 to update / upgrade of an existing product. Only those components are removed, which are no longer used. This ensures the shortest installation time. Option 1 and 2 can be used to replace application 1 by application 2. This is often used e.g. to replace WordPerfect by Word. Option 3 is almost not used. Examples of possible errors: InstallExecuteSequence Table (example with option 2):
You could solve this error: Between 'InstallInitialized' and 'RemoveExistingProducts' there may be nog actions that execute so-called 'script actions' (Registration, Publication, Installation (file copy tasks)). It is better to have NO actions between these two actions. |
|||||||||||||
» Back to article overview