Tobias, that is the approach which I use, embedding the language transforms and setting MsiProperty TRANSFORMS=:langid.mst. I thought that I had tested this successfully several months back when using Wix 3.8, but now I am see two problems documented above. Once installed, say with the German :1031.mst transform later when the bundle is launched to do an uninstall, the plan shows that the package is absent. Also seeing problems with on-demand installs, which I am certain was working in the same scenario with Wix 3.8. so I am curious if others are seeing these issues, or if I should just not try to use language transforms with Burn.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7596923.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
