I would assume it would be as easy as adding a MsiProperty element. <MsiProperty Name="TRANSFORMS" Value=":[UserLanguageId].mst" />
This assumes you have a transform embedded in the MSI for each possible language. If it's external, remove the ":" and add a series of Payload elements to the MsiPackage for each supported language. I don't think there is any easy way to fall back to a default transform if you don't have one for the specific language. -----Original Message----- From: Helge Kruse [mailto:helge.kr...@gmail.com] Sent: Wednesday, February 27, 2013 6:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Using burn for installer localization > In theory, you should be able to pass UserLanguageID or > SystemLanguageID as a MsiProperty to apply a transform to a MSI > package. This was my idea. But the question was about a pointer to information how to do this. Can similar be read in any example project? Regards Helge ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
