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: Embedding language MSTs in 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
‎Jul 19, 2010
04:48 AM
Embedding language MSTs in MSI
How can I tell InstallShield 2010 Premier to include the selected language MST files in the built MSI instead of creating them separately?
And if they are included in the MSI, how can I choose the correct language when I launch the MSI through InstallScript using msiexec?
And if they are included in the MSI, how can I choose the correct language when I launch the MSI through InstallScript using msiexec?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 21, 2010
06:36 PM
Answering in reverse order, you can specify the language transform to use by passing the TRANSFORMS=something.mst property at the msiexec command line.
I don't know if InstallShield will put the transforms inside the MSI database, though. Microsoft's Windows Installer SDK has a script that will embed transforms in the MSI, and TRANSFORMS supports the :something.mst syntax for applying embedded transforms, but that might need to happen as a post-build step.
I don't know if InstallShield will put the transforms inside the MSI database, though. Microsoft's Windows Installer SDK has a script that will embed transforms in the MSI, and TRANSFORMS supports the :something.mst syntax for applying embedded transforms, but that might need to happen as a post-build step.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 09, 2011
07:36 PM
last year I was using IS 2010 Premier and had a basic-MSI project with 2 languages in addition to English, and the release was set to include all 3 as UI languages, and I got a simple .msi output, no .mst files.
Now I'm running IS 2011 Premier, and have incorporated MSI-chaining and Release Flags into my basic-MSI project. If I have more than one language selected for UI languages, I can't seem to generate JUST a .msi file without those .mst files.
What changed from last year? Based on this thread it sounds like outputting these .mst files is the expected behavior, but I don't understand then why I didn't get them last year. Is there a setting in the Installshield options to control this? I would turn off the UI languages, as this build is meant for a silent installation anyway, but then all my start menu shortcut strings (and other misc. strings such as file association descriptions) don't get localized at all.
Now I'm running IS 2011 Premier, and have incorporated MSI-chaining and Release Flags into my basic-MSI project. If I have more than one language selected for UI languages, I can't seem to generate JUST a .msi file without those .mst files.
What changed from last year? Based on this thread it sounds like outputting these .mst files is the expected behavior, but I don't understand then why I didn't get them last year. Is there a setting in the Installshield options to control this? I would turn off the UI languages, as this build is meant for a silent installation anyway, but then all my start menu shortcut strings (and other misc. strings such as file association descriptions) don't get localized at all.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)