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
- :
- Chained msi and pre-requisites
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
Dec 10, 2012
11:04 PM
Chained msi and pre-requisites
:confused: Hi,
My requirement is to have a single msi installer, which will in turn install couple of other msi packages, and VC++ Redistributable, and SQLExpress (both of them are .exes, which later invokes .msi).
I've added Msi packages as chained msi, and exe as pre-requisites. but since ive prerequisites, my build output is not an msi, but an exe.
If I add the exes to install during custom actions.. I'm not able to do a silent installation of the whole package on Windows 7.
It complains of having two exection sequence trying to run in parallel.
Is there a way to get out of this situation.
Any thought is appreciated...
Thanks.
My requirement is to have a single msi installer, which will in turn install couple of other msi packages, and VC++ Redistributable, and SQLExpress (both of them are .exes, which later invokes .msi).
I've added Msi packages as chained msi, and exe as pre-requisites. but since ive prerequisites, my build output is not an msi, but an exe.
If I add the exes to install during custom actions.. I'm not able to do a silent installation of the whole package on Windows 7.
It complains of having two exection sequence trying to run in parallel.
Is there a way to get out of this situation.
Any thought is appreciated...
Thanks.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 11, 2012
04:08 AM
As soon as you decide on single MSI installer you have to limit yourselves to so many things.
Launching an installer can only be done as a chained MSI as silent installs will skip the custom actions in UI and execute actions can't go with second MSI process.
only way is chained MSI in your scenario and I cant seem to find a way out of it.
Launching an installer can only be done as a chained MSI as silent installs will skip the custom actions in UI and execute actions can't go with second MSI process.
only way is chained MSI in your scenario and I cant seem to find a way out of it.
