Yes the LCIDs are used in the WiX context for wxl files, but in the .Net context of the managed BA two letter culture or culture-Region tags are used.
I think that there are two areas where issues are likely. 1) Validating that your DLL is at the path from which the app is trying to load it. Use ProcessMon to see where it is trying the load the DLL from and adjust the WiX Payload element to match that path. 2) You may still get the .Net exception if the namespace path in the code does not match the namespace that the compiler assigned. I had issues with that step and ILSpy was helpful in looking at my DLL and seeing what the C# compiler had used for a namespace and then adjusting my code to match the namespace. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-Managed-BA-tp7597813p7597900.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
