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
- :
- VBScript after chained msi
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
Nov 18, 2011
05:38 AM
VBScript after chained msi
Hello!
I´m testing IS2012 right now and I´m trying to build a basic msi-project with chained msi-packages.
The installation and the chained msi files are working like a charm, now I´m getting in trouble setting up a custom action that runs a vbscript after the installation of the chained installers.
I think I don´t understand the whole sequence settings. I like to execute my VBS-File right after the last chained msi-package is installed.
Which settings do I need to apply? In which sequence do I have to put my CA?
Thank you in advance!
Greetings from Germany
Borsti aka Sebastian
I´m testing IS2012 right now and I´m trying to build a basic msi-project with chained msi-packages.
The installation and the chained msi files are working like a charm, now I´m getting in trouble setting up a custom action that runs a vbscript after the installation of the chained installers.
I think I don´t understand the whole sequence settings. I like to execute my VBS-File right after the last chained msi-package is installed.
Which settings do I need to apply? In which sequence do I have to put my CA?
Thank you in advance!
Greetings from Germany
Borsti aka Sebastian
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 23, 2011
01:57 PM
It's been a while since I had my head fully wrapped around this, but I think the only part of the main MSI which executes after any of the chained packages is its commit or rollback phase of the InstallExecuteSequence. And even that may not be completely after; its commit phase may be before the chained packages' commit phase, but it will be after all the immediate and non-commit, non-rollback deferred actions.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)