I'm new to multilanguage and I'm trying to understand something.   

Scenario:  A WiX installer that has language transforms and a bootstrapper to 
select the transform but also consumes multilanguage merge modules with their 
own localization transforms for things like ShortCuts and Service Names.

What does the integration of this look like?  Will WiX merge those embedded MSM 
transforms into the resulting MSI?   Do you have to call each one of them 
specifically with TRANSFORMS= ?

Sorry, very new to this side of MSI.

Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves 
attention? E-Mail Me


--- On Mon, 3/8/10, Fan Zhang (UPG) <fanz...@microsoft.com> wrote:

> From: Fan Zhang (UPG) <fanz...@microsoft.com>
> Subject: Re: [WiX-users] Single msi with multi languages installs according 
> to OS display language
> To: "General discussion for Windows Installer XML toolset." 
> <wix-users@lists.sourceforge.net>
> Date: Monday, March 8, 2010, 5:56 PM
> Hi Mike,
> 
> Thanks for your reply! Good to hear that wix3.5 will soon
> have a bootstrapper. As for now, do I need to write a
> console application which reads OS display language and then
> passes it to msiexec? I looked at bootstrapper in MSBuild
> with examples like below. However, it is not clear to me how
> things work for me (as this bootstrapper installs
> prerequisites, plus culture is hard coded, while my case
> wants language parameter be passed to the only msi at
> install-time).
> 
> <Project DefaultTargets="Build" 
> xmlns="http://schemas.microsoft.com/developer/msbuild/2003";
> ToolsVersion="3.5">
>   <ItemGroup>
>     <BootstrapperFile
> Include="Microsoft.Windows.Installer.3.1">
>       <Visible>TRUE</Visible>
>       <ProductName>Windows Installer
> 3.1</ProductName>
>       <Install>true</Install>
>     </BootstrapperFile>
>   </ItemGroup>
> 
>   <Target Name="Bootstrapper">
>     <GenerateBootstrapper
>       ApplicationFile="MMM.exe"
>       ApplicationName="MMM "
>      
> BootstrapperItems="@(BootstrapperFile)"
>       OutputPath=".\"
>       ComponentsLocation="Relative"
>       Culture="en"/>
>   </Target>
> </Project>
> 
> Please let me know if you have any further information or
> instruction. Thanks for your help!
> 
> Thanks,
> Fan
> 
> -----Original Message-----
> From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com]
> 
> Sent: Monday, March 08, 2010 10:56 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Single msi with multi languages
> installs according to OS display language
> 
> You need to use a bootstrapper (an EXE designed for running
> one or more installation packages) that will pass the
> appropriate language property to the MSI at install-time.
> 
> WiX 3.5 will have a bootstrapper called Burn, but it's
> still under development right now.
> 
> Thanks,
> Mike Carlson
> 
> -----Original Message-----
> From: Fan Zhang (UPG) [mailto:fanz...@microsoft.com]
> 
> Sent: Monday, March 08, 2010 10:33 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Single msi with multi languages
> installs according to OS display language
> 
> Hello,
> 
> I want to make a single msi with multi languages including
> en-us, de-de, zh-cn, etc. When the msi is installed, it
> installs according to OS display language. By following
> instructions at "9.1 Morphing Installers" at 
> http://www.tramontana.co.hu/wix/lesson9.php#9.1. I can
> do it manually like below:
> 
> torch -p -t language "en-us\MMM.msi" "de-de\MMM.msi" -out
> de-de.mst
> EmbedTransform "en-us\MMM.msi" de-de.mst
> msiexec /i "en-us\MMM.msi" TRANSFORMS=":de-de.mst"
> 
> If I want the msi choose language automatically according
> to the current OS display language. Do you know how can I
> achieve it?
> 
> Thanks,
> Fan
> 
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling,
> find bugs
> proactively, and fine-tune applications for parallel
> performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling,
> find bugs
> proactively, and fine-tune applications for parallel
> performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling,
> find bugs
> proactively, and fine-tune applications for parallel
> performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 


      

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to