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
- :
- Call exe(s) or msi(s) during installation
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 21, 2008
07:50 AM
Call exe(s) or msi(s) during installation
I am pretty new to InstallShield.
I have to write an installer which installs the main application and depending on user selection, a database (SQLServer2005) and drivers for a few smartcard readers.
I started with an "InstallScript MSI Project". I was able to define SQLServerExpress2005 as prerequisite. But how do I call the installers for the smartcard readers based on msi?
Is it not possible to call an msi within an installscript msi project?
Would I be better of using an "InstallScript Project"?
Any help is welcome.
I have to write an installer which installs the main application and depending on user selection, a database (SQLServer2005) and drivers for a few smartcard readers.
I started with an "InstallScript MSI Project". I was able to define SQLServerExpress2005 as prerequisite. But how do I call the installers for the smartcard readers based on msi?
Is it not possible to call an msi within an installscript msi project?
Would I be better of using an "InstallScript Project"?
Any help is welcome.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
โJan 21, 2008
10:28 AM
It is and it isn't possible. ๐
There are two mutex's in MSI. One that prevents two concurrent excecute sequences per machine and one that prevents two concurrent UI sequences in the same process.
If you don't need/want to support a silent install ( execute sequence only ) it's possible to shell out of process from within UI sequence #1 to call install #2. If you need/want ( highly reccomended ) to support a silent install then it can't be done. This is where the use of a bootstrapper comes so that you can chain MSI's together before you are inside an MSI.
The problem is the story isn't complete to support this type of relationship. This is where MSI 4.5 is trying to improve things.
http://blog.deploymentengineering.com/2007/06/msi-45-and-better-together-pattern.html
There are two mutex's in MSI. One that prevents two concurrent excecute sequences per machine and one that prevents two concurrent UI sequences in the same process.
If you don't need/want to support a silent install ( execute sequence only ) it's possible to shell out of process from within UI sequence #1 to call install #2. If you need/want ( highly reccomended ) to support a silent install then it can't be done. This is where the use of a bootstrapper comes so that you can chain MSI's together before you are inside an MSI.
The problem is the story isn't complete to support this type of relationship. This is where MSI 4.5 is trying to improve things.
http://blog.deploymentengineering.com/2007/06/msi-45-and-better-together-pattern.html
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)