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: Chain a multilanguage setup
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
‎Oct 13, 2011
10:51 AM
Chain a multilanguage setup
Hi all,
I have built 2 setup (setupA.exe and setupB.exe) with Installshield 2008 (Basic MSI Project).
I would like to launch setupB during the setupA and I would like to know the best way to do this?
I have already done it by launching the msi file from the setupB with a custom action, however I lost the language selected in the setupA and the setupB display the default language and not the one selected by user.
Thanks for your help
I have built 2 setup (setupA.exe and setupB.exe) with Installshield 2008 (Basic MSI Project).
I would like to launch setupB during the setupA and I would like to know the best way to do this?
I have already done it by launching the msi file from the setupB with a custom action, however I lost the language selected in the setupA and the setupB display the default language and not the one selected by user.
Thanks for your help
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2011
11:08 AM
Hi There,
Try adding on the command line to the second setup:
setup.exe /s /L[ProductLanguage]
For MSI setups, /L uses the same type of language ID as the MSI engine, so you can pass it through.
Try adding on the command line to the second setup:
setup.exe /s /L[ProductLanguage]
For MSI setups, /L uses the same type of language ID as the MSI engine, so you can pass it through.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 14, 2011
03:14 AM
Hi,
Thanks for your advice, but I needed a little more help to configure the custom action.
I have added the setupB in the list of Support Files in order it is included in the setup package but not installed.
I have set a custom action with the following properties but it fails to install and uninstall properly:
- Executable Protperty : SOURCEDIR
- Command Line : SetupBFolder\setupB.exe /L[ProductLanguage]
- Return processing :Synchronous (Check exit code)
- In-Script Execution : Immediate Exection
- Execution Scheduling : Execute only once
- Install UI Sequence :After Cost Finalize
Regards
Thanks for your advice, but I needed a little more help to configure the custom action.
I have added the setupB in the list of Support Files in order it is included in the setup package but not installed.
I have set a custom action with the following properties but it fails to install and uninstall properly:
- Executable Protperty : SOURCEDIR
- Command Line : SetupBFolder\setupB.exe /L[ProductLanguage]
- Return processing :Synchronous (Check exit code)
- In-Script Execution : Immediate Exection
- Execution Scheduling : Execute only once
- Install UI Sequence :After Cost Finalize
Regards
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 14, 2011
07:14 AM
I've finally succeed to build my setup.
I have generated one setupB.exe file and include it in the binary table of setupA.
From SetupA custom action, I browse the setupB.exe file and give only the command line options in Target field and keep other options.
Everything seems to work fine.
Regards
I have generated one setupB.exe file and include it in the binary table of setupA.
From SetupA custom action, I browse the setupB.exe file and give only the command line options in Target field and keep other options.
Everything seems to work fine.
Regards