Tim; I took your wxs file and added it to a new WiX bootstrapper setup project (in VS2010). I tried to recreated your file tree as closely as possible and I stripped out the code that was not related to testing whether the localized files were displayed, without needing to provide the -lang switch.
For the file tree I used RTF files that I have and a simple MSI test package. Since my test box is currently configured to test either English or German, for simplicity I eliminated the other languages. But otherwise I tried to use your code as you presented it. I tested this on Windows 8 x64, which is configured to set the SystemDefaultLanguageID based on the UserDefaultLanguageID. And it is configured to set the UserDefaultLanguageID to the top item in the Input Language display list. First I built the package using Wix 3.8.722 and tested it with German set as the Default Language, successfully. Then I changed to English for the default language, and the English dialog was displayed successfully. Then I reconfigured my build box to build the project using WiX 3.7.1224. I tested this build in the German configuration, and it displayed the German dialogs and German EULA successfully. Then I switched the default to English and ran the setup. It detected and displayed the English dialogs and EULA successfully. Actually this surprised me, as I thought I would have to convert your code to use the WixExtenededBootstrapperApplication in WiX 3.7 for this to work. But that was not necessary. However my WiX 3.7.1224 does have the WixBalExtensionExt.dll from: http://wixextba.codeplex.com/releases/view/105895 which I copied to my WiX 3.7.1224\bin folder. So maybe when Neil says that there was a bug in 3.7 which is fixed in the Extended Bootstrapper, it is only necessary to have his DLL in the Wix 3.7 bin folder to get the fix, without actually using the WiXExtendedBA UI. I will have to research this further. I will try to attach a zip package of the project as I built it. Test_SmartTable.txt <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588148/Test_SmartTable.txt> If it works you will find both the 3.7 and the 3.8 build which I tested. Because of the antivirus configuration on our network I had to sign the test builds with my certificate, but I removed those steps from the archived project. Bottom line is I don't know if this is all that helpful since it does not explain your observations, but your code does automatically display the translated EULA for me. Phill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7588148.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
