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: calling an msi from 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
Aug 09, 2009
05:46 AM
calling an msi from msi
hello,
I have the following issue:
I want to run an msi that calls another msi installation during runtime. Is there a way to do that using InstallShield?
and, can I check previous installed versions of those msi I need to add to my installation?
edit:
for clarification, in the following link http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q105706&sliceId=
last paragraph, what does "Executable custom actions that run msiexec.exe are the recommended method of installing a child MSI package" mean?
I have the following issue:
I want to run an msi that calls another msi installation during runtime. Is there a way to do that using InstallShield?
and, can I check previous installed versions of those msi I need to add to my installation?
edit:
for clarification, in the following link http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q105706&sliceId=
last paragraph, what does "Executable custom actions that run msiexec.exe are the recommended method of installing a child MSI package" mean?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 09, 2009
07:03 PM
If you're using InsallShield 2010, you might consider launching the second MSI package as a prerequisite (either an InstallShield prerequisite or a feature prerequisite) or as a chained installation.
(The old "executable custom actions" comment suggests to launch msiexec.exe with a "launch an EXE" custom action, but that's limited to launching from the User Interface sequence, which in turn runs into problems with silent installations, elevated privileges, and so forth.)
(The old "executable custom actions" comment suggests to launch msiexec.exe with a "launch an EXE" custom action, but that's limited to launching from the User Interface sequence, which in turn runs into problems with silent installations, elevated privileges, and so forth.)