I am trying to solve that same issue, so I do not have a solution yet. I was in the process of importing the 'extended bootstrapper' and writing a BAFunction.dll to try and get the language of the UI to be the same as the OS UserLanguageID and also address an issue where I need to restrict which LCIDs get passed to my MsiPackage as a name of a transform. This morning I got a message from the extended bootstrapper site that implied that Wix 3.8 resolves the first part of this issue and showes the bootstrapper language based on the OS settings. So I am now working on checking out that lead. Bottom line is I don't have this issue figured out yet.
Check out: http://wixextba.codeplex.com/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587946.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
