This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Chained MSI's - Minimum Set of Custom Actions/Sequences?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 07, 2010
05:02 PM
Chained MSI's - Minimum Set of Custom Actions/Sequences?
I was wondering if anyone could point me toward something (aside from trial and error) that would outline what the minimum set of actions/custom actions is for the Execute sequence?
In short, I'm using a simple InstallScript MSI executable to fire a set of Chained MSI's, and I want to eliminate as many of the extraneous Actions that it must cycle through before it actually begins to fire the first MSI.
Obviously, Actions such as ISSetupFilesExtract, ISChainPackage* and ISSetupFilesCleanup will be needed, but, being that this project does absolutely nothing (aside from install some prerequisites) except fire the MSI's, how much of the other stuff can I get rid of? Do I need to bother having it do Costing, etc..?
Any help & insight is greatly appreciated.
In short, I'm using a simple InstallScript MSI executable to fire a set of Chained MSI's, and I want to eliminate as many of the extraneous Actions that it must cycle through before it actually begins to fire the first MSI.
Obviously, Actions such as ISSetupFilesExtract, ISChainPackage* and ISSetupFilesCleanup will be needed, but, being that this project does absolutely nothing (aside from install some prerequisites) except fire the MSI's, how much of the other stuff can I get rid of? Do I need to bother having it do Costing, etc..?
Any help & insight is greatly appreciated.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 18, 2010
09:41 AM
In case anyone wonders the answer to this as well, I was able to reduce the number of actions in the Execute Sequence to the following (and it may be able to be further reduced):
ISSetupFilesExtract
LaunchConditions
FindRelatedProducts
ISPreventDowngrade
ValidateProductID
CostInitialize
FileCost
ResolveSource
setUserProfileNT
setAllUsersProfileNT
setAllUsersProfile2K
CostFinalize
InstallValidate
ISChainPackagePrepare
InstallInitialize
ISChainPackageRollback
ISChainPackageCommit
InstallFinalize
ISSetupFilesCleanup
FYI: This is for an InstallScript MSI in IS2009 and it is simply a wrapper exe to spawn a bunch of Chained MSI's.
ISSetupFilesExtract
LaunchConditions
FindRelatedProducts
ISPreventDowngrade
ValidateProductID
CostInitialize
FileCost
ResolveSource
setUserProfileNT
setAllUsersProfileNT
setAllUsersProfile2K
CostFinalize
InstallValidate
ISChainPackagePrepare
InstallInitialize
ISChainPackageRollback
ISChainPackageCommit
InstallFinalize
ISSetupFilesCleanup
FYI: This is for an InstallScript MSI in IS2009 and it is simply a wrapper exe to spawn a bunch of Chained MSI's.