As Neil indicated you have to provide correct names in your Payload attributes.
Here is another discussion about this issue: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-theme-in-Bundle-how-to-add-xml-and-wxl-td7588021.html#a7588026 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html#a7587783 Part of the problem that I originally had was that I did not understand how the language configuration behavior in the OS had changed from Windows 7 to Windows 8. I was testing on Windows 8. Also I started working with Wix 3.7. Others then pointed out has a bug related to the language selection, which is fixed in Wix 3.8. So I got all of this working on XP through Win 8 using Wix 3.8 and the above information. ProcessMon was my friend. The BA and related files are typically extracted to a folder under your %temp% folder. So you can use ProcessMon to watch where the BA is trying to load your localized file from and what name it is trying to use. It can work. I would also enable verbose logging (<Property Id='LOGVERBOSE'>1</Property>) and tracing in your project properties. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-I-localize-Bundle-Name-in-bootstrapper-project-tp7592104p7592710.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
