Sorry for reviving a fairly old thread, but I'm working on localizing the MSIs inside a bundle and the following made me a bit uneasy:
I use a single localized bootstrapper and separate localized msi(s). All of > my UX GUI is in the mba, except for a few status and error messages in the > MSI. I used to try to embed the culture transforms into a single msi. > That > resulted in very subtle problems, and I was told that is not supported when > using a Burn bootstrapper. I would not advise going down that path. > Phill, are you saying that it's impossible to create a single MSI with multiple cultures? Do you happen to still have any references to the "subtle problems" that you mention? We're shipping a bundle exe for our product, but in certain situations, such as deployment via GPO, our end-users must use MSIs, which means we need to localize both the bundle *and* the MSI. I would very much want to avoid having to bundle 17 almost-identical MSIs in a bundle if possible... Thanks, Soren On Tue, Jan 13, 2015 at 7:01 AM, Phill Hogland <phogl...@rimage.com> wrote: > Here are a couple of quick links (and there are many more on this topic): > When this link was posted I was using WixStdBA > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html#a7587770 > > Here I use an mba, but the same concepts can be done in WixStdBa > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-td7596896.html#a7598508 > > I use a single localized bootstrapper and separate localized msi(s). All > of > my UX GUI is in the mba, except for a few status and error messages in the > MSI. I used to try to embed the culture transforms into a single msi. > That > resulted in very subtle problems, and I was told that is not supported when > using a Burn bootstrapper. I would not advise going down that path. > > Others have discussed in this forum how to ship a single localized > bootstrapper and a single msi with multiple transforms applied by the > bootstrapper. Each culture specific MSI must be built to create the > transforms. Typically a single 'package' project is used and you set the > cultures as documented in chm which results in MSBuild batch building the > different culture specific outputs. > > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7598843.html > Sent from the wix-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
