Not necessarily exactly this issue. In MSI, the order that the various transforms are applied is key. When I investigated using transforms, I didn't discover the page on MSDN that describes the order that combining transforms and patches on a commandline (or later, when adding more patches) would present themselves (I don't recall if I found that page later on or not, because in the end the complexity involved wasn't something I wanted to tackle at the time). It is possible to setup transforms (including those in patches) to ignore the language settings of their targets, but that isn't always a good idea, especially if you don't have total control over the way others carry out deployments of your code (they would succeed at applying your German patch on your French transform, which is likely never a good thing).
As a result, we stepped back and thought about how else we could address our goals, and in the end the only transforms we use are those embedded inside the patches we use for servicing. We use an external UI (no dialogs in the MSIs) and thus avoid all the issues surrounding MSI and its weak IU primitives and font problems associated with using UTF-8 (required in the MSIs to deploy in several languages we support). Our latest move is to use separate MSIs for the loc-specific stuff to reduce our servicing costs as well as our deployment costs associated with adding new languages post-release and to enable MUI deployments (more than one language installed side-by-side). It has the benefit of reducing build times by 4-6 hours as well. Our software has a consumer rather than an enterprise orientation, so Group Policy deployment wasn't considered an issue, but if both MSIs are present and included in the push, it should still work. MSI 4.5 would help there with the transactional chaining it provides as it can reference both MSIs in the transaction. -----Original Message----- From: Gareth [mailto:gmor...@serif.com] Sent: Wednesday, September 23, 2009 9:48 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Multi language patching So, you've seen this behaviour before and agree that there's an MSI limitation relating to language specific files in a multi language package? I'm just really interested to know if the patch failures I've seen are because of the language specifications. Blair-2 wrote: > > We avoided this headache... > -- View this message in context: http://n2.nabble.com/Multi-language-patching-tp3700410p3700931.html Sent from the wix-users mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
