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: ISInstallPrerequisites
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
‎Aug 25, 2011
08:39 AM
ISInstallPrerequisites
Hello
is it possible to put CA ISInstallPrerequisites into
Execute Sequence?
Thanks
is it possible to put CA ISInstallPrerequisites into
Execute Sequence?
Thanks
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2011
10:33 AM
Yes and no. There's nothing about the MSI tables that would prevent this. However if you do so, many prerequisites would be likely to fail due to MSI running only a single execute sequence at a time.
But to really answer, why would you want ISInstallPrerequisites in the execute sequence? If it's for silent installations, you need to kick those off through setup.exe or install the prerequisites manually. Is this something that would be better handled by a suite installation?
But to really answer, why would you want ISInstallPrerequisites in the execute sequence? If it's for silent installations, you need to kick those off through setup.exe or install the prerequisites manually. Is this something that would be better handled by a suite installation?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2011
01:27 PM
Hello,
yes it should work as silent msi-setup without exe wrapper.
yes it should work as silent msi-setup without exe wrapper.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2011
02:23 PM
Once upon a time I wrote a non-traditional bootstrapper using a Basic MSI project. To get around the mutex limitations in Windows Installer ( one execute sequence per machine and one ui sequence per process ) and still meet the spirit of a non-interactive installation experience I did the following:
Per CA's in the UI sequence after the Execute action that created processes to run the chained MSI's in.
Ran the `bootstrapper` with /QR instead of /QB. This processes the UI sequence but skips the authored dialogs. It wasn't perfect but it made everyone happy for 5-6 years ( and counting ).
Per CA's in the UI sequence after the Execute action that created processes to run the chained MSI's in.
Ran the `bootstrapper` with /QR instead of /QB. This processes the UI sequence but skips the authored dialogs. It wasn't perfect but it made everyone happy for 5-6 years ( and counting ).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 26, 2011
10:12 AM
Hello Christopher,
it is all true, what do you write.
But my setup should runs in silent mode, without setup.exe, too.
So, if I decide to write own wrapper for startting a chain of msi setups at the end of main installation, I would put it in execution seq.
There are szenarios:
1. Normal installation with UI:
wrapper starts after Dialog "Setup success"
2. Silent installation without UI:
wrapper starts at the end of main setup
it is all true, what do you write.
But my setup should runs in silent mode, without setup.exe, too.
So, if I decide to write own wrapper for startting a chain of msi setups at the end of main installation, I would put it in execution seq.
There are szenarios:
1. Normal installation with UI:
wrapper starts after Dialog "Setup success"
2. Silent installation without UI:
wrapper starts at the end of main setup
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)