You can do it that way, but there are other approaches. For most of my MSIs I use the EmbedTransforms tool as described here: http://wix.tramontana.co.hu/tutorial/transforms/morphing-installers
Then I just deploy the the MSI without any payloads. MSI automatically selects the embedded transform if they are named with a leading colon. :1033.mst, etc I have a third-party MSI where I include the transforms as Payloads as you did. When using a bootstrapper with localization files, the wxl file related to the system's culture (depending on OS behavior which is a bit different in Win 8 and later) is selected. I created a ' Transform' string in the wxl file which is then passed to the MSI as a property to select which transform payload to use. But that is basically the approach you are taking. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-select-msi-and-apply-mst-dynamically-tp7593970p7593980.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees_APR _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
