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
- :
- Run another install package with Support Files
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
‎Mar 10, 2011
10:19 AM
Run another install package with Support Files
Hi to all,
i'm trying to run a third part package (made with the old vb6 installer ) from my MSI install pack. I've add 3 files on Support Files->language Independent (SETUP.LST, setup.exe, mypack.CAB)
I've add a custom action Launch an Exe, path referencing a directory
Working directory = SUPPORTDIR
Filename and command line field = "[SUPPORTDIR]\setup.exe"
In-script execution = Commit execution
Install Exec Sequence = After Install Files
The installation of the third part pack doesn't run as expected.....why? No errors...
Thank you.
i'm trying to run a third part package (made with the old vb6 installer ) from my MSI install pack. I've add 3 files on Support Files->language Independent (SETUP.LST, setup.exe, mypack.CAB)
I've add a custom action Launch an Exe, path referencing a directory
Working directory = SUPPORTDIR
Filename and command line field = "[SUPPORTDIR]\setup.exe"
In-script execution = Commit execution
Install Exec Sequence = After Install Files
The installation of the third part pack doesn't run as expected.....why? No errors...
Thank you.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2011
10:03 PM
What if you place the custom action to UI Sequence?
If sub-installation works fine,the possible cause is Windows installer's limitation.
Execution sequence can launch only one msi file.
If sub-installation works fine,the possible cause is Windows installer's limitation.
Execution sequence can launch only one msi file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 18, 2011
04:49 AM
I've resolved with a bat file that launch the 2 packages (1 msi and 1 exe)
Thank you.
Thank you.