Sorry to confuse, The localization variables are just the ones defined in the unmanaged bootstrapper that runs when a .NET 4.0 dependency exists (i.e. .NET 4.0 is not present on the target system). I handle translations myself in the Windows forms portion of the custom managed bootstrapper UI.
I am not 100% sure that I am referencing the .wxl files properly for the custom BA. I am doing it the only way that I can figure out how. The "Cultures to Build" textbox in the Build properties for the Bootstrapper application is disabled or read-only, I cannot specify anything in there. My understanding is that if it is blank, then it will build all provided localizations. I am using Visual Studio 2010 to build my app and the msi, bootstrapper, etc. I just specify the locale in the appropriate section of my .wxl files and that is all I can figure out to do. My understanding is that if you provide the .wxl files as part of the bootstrapper project and Cultures to Build is blank it should just build them all. If there is something missing on my part, I would be happy to fix it, but I cannot find any info that is helpful about this error. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Localization-Identifiers-Duplicated-tp7586776p7586863.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
