There should not be a problem with Product Codes as I am using the same .msi in both MsiPackage entries, not multiple msi's that are language specific.
I have again just the one .msi and the language .mst's files. So if one of the supported languages exists it will trigger the first MsiPackage ID and pass in the correct TRANSFORMS=[SystemLanguageID].mst. If the language of SystemLanguageID is not supported it will trigger the 2nd MsiPackage ID and simply pass in TRANSFORMS=1033.mst. So again I have tested with supported and non-supported language OS's and it seems to work. So it should be good. Tim. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7587227.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
