There are different approaches to doing localization in a managed context, and since this is a .Net issue and not specifically related to WiX I did not find a specific document with steps on how to do it. Yes I localize my mba for en, de, es, it, ja, and zh. My approach was a little different than yours but I think the core issues remains the same. I am not using satellite DLLs. My resource strings are embedded resources. Even so a wix mba DLL gets loaded into a host provided by wix. And while it was about a year ago that I got this stuff working, and I was very knew to C# at the time and may not have understood what I was doing, I had to define a different namespace for my strings 'myRes', rather than using the default 'resources' namespace which already existed. ILSpy was helpful in sorting that out.
I think Sean had a good suggestion (with documentation). Did you try: <Payload SourceFile="..\Translation\lib\Release\en-US\Agilent.OpenLAB.Installation.resources.dll" Name="en-US\Agilent.OpenLAB.Installation.resources.dll"/> -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-Managed-BA-tp7597813p7597891.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
