Thanks for the response... No we are not going to be showing the MSI in UI. What is in the language .mst files are the application shortcuts. The names of the shortcuts are translated and therefore if say you are on a french machine then we want the shortcuts to be in French...
We have not looked at embedding the .mst's in the MSI. How do we accomplish that step? So once we get the .mst's embedding into the .msi then we can use the following method to trigger the install to use the correct embedded .mst: <MsiPackage ...> <MsiProperty Name="TRANSFORM" Value=":[TransformFileName].mst" /> </MsiPackage> Where the [TransformFileName] = SystemLanguageID? If we only support selective languages then in the bundle how do we condition the value of TransformFileName to only be one of the supported languages and if SystemLanguageID is not a supported language then we set it to English? Thanks again for your help. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7586997.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
