Okay I have not yet figured this out. I have tried placing the calling of my MsiPackage into a separate Fragment file and add a property definition to default language and then conditioned custom actions for the supportted languages, but it looks like Burn completely ignores this default property and custom actions and therefore when triggering the .msi with TRANSFORM= in the command line that it will fail as it is not filling in the languageID .mst.
So again could I get a simple example on how to create a Burn custom action (BA) or pointed in the correct direction that will provide some help in how to create a BA? Just as a note I do not have much programming language experience and the little that I do is with C++. So examples in C++ would be perferable. If not then what ever I get then I'll pass on to other developers that my have experience in other languages. Thanks again for any help on this issue. 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-tp7586986p7587202.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
