[wix-users] Localization

[Parkes, Kevin]

How 'bout dat... I knocked together some test projects and the approach described seems to work perfectly.

Many thanks

Kev

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Phill Hogland
Sent: 09 February 2016 14:59
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] Localization

I originally went down the path of having a Burn driven chain of MSIs (each of which was the 'base language' built for a MSI project with language transforms embedded using EmbedTransfroms.exe).  And while this appeared to work I discovered some unacceptable behaviors when an 'on-demand' install of an MSI was launched on a non-base language configuration, typically due to an advertised feature.  When researching this the advice that I got was that Burn does not support the use of MSIs with embedded transforms in this manner.  The transform ends up changing the markers (or thumbprint) used by Burn to ID the MSI package after installation, so it becomes a similar problem as using Instance Transforms, which I believe is not yet supported by Burn.  So I changed my approach as described here in a post to the old wix-users forum.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-td7596896.html#a7598508

(While searching the current wix-users forum has had some issues and is not very useful, searching the old wix-users forum is a great resource for finding solutions!)

Later others described in the old wix-users forum, how they ship a base-language MSI and also list each Language Transform in the chain so that Burn apples the language transforms.  I did not try that approach.

Phill

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Parkes, Kevin
Sent: Tuesday, February 09, 2016 4:54 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Localization

I currently have a single, monolithic MSI which I want to split up and then create a bundle.

The MSI includes embedded transforms for language support and my initial idea was to have "core" files in one MSI and languages in separate ones. However, I need to create things like shortcuts and context menu items which obviously have to be localized and reference the EXE in the core MSI. Is there a standard/recommended approach for something like this?

Thanks



____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/