2. Is there any scope for making this optional or replacing Product/@Id="*" on the first pass of light? The PackageCode is not regenerated on every run of light, is this not the same?
I can't find any good documentation on Windows Installer localisation, do you think I am doing the right thing to localise my install or is it my approach that is floored. Thanks Neil -----Original Message----- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: 01 December 2008 20:12 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Localisation 1. Don't know. 2. If you use Product/@Id="*" then it always generates a new ProductCode. If you don't want that, don't use "*". 3. No. There are cases where you'll end up with a binary .wixout even if you don't use -bf, especially around the use of CustomActions. -----Original Message----- From: Neil Sleightholm [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2008 10:34 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Localisation Having worked through a few bugs in light I am now back to looking at this problem again. What I would like to do is create an MSI with a separate transform (MST) for each language. So the process I intend to use is: 1. Create wixout for my install using the -sloc parameter. 2. Link the wixout to create the English MSI. 3. For each language run light on the wixout to create a new translated MSI or wixout. 4. Use torch to create an MST for each language from 3. Until the next WiX release I am not able to try this but I can see a couple of problems: 1. The documentation for torch says that if you use a wixout input file it will only create a wixout (-xo set by default if -xi set). Is this correct? If it is, how do you create an MST from a wixout? 2. Every time I run light it will create a new product code but I don't want that, I want one product code and simply install with a different UI language. From what I have read this seems to be a valid approach. Can anyone suggest how I can do this? 3. I thought I could solve 2 but editing the wixout file and putting in my own ProductCode so that it is not regenerated but it appears to start with some binary data. I think that it is always binding the files into wixout not just when -bf is used. Does this sound like a bug? Thanks for your help Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] -----Original Message----- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: 06 November 2008 22:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Localisation 0. *Every* MSI should have a different PackageCode. Even two builds of the same MSI. 1. You *can* have different ProductCodes for all of your languages. Depends on what your SxS story is. 2. The most efficient way I've seen this done is: a. Link to ".wixout" files. This will get you everything but the final localized build. b. Use cab cache to minimize the number of cabinets rebuilt. If you are really careful with your Media elements this can lead to huge savings. c. Link the ".wixout" file with each ".wxl" file in turn, to build the final MSI files. d. Use torch to build transforms from all of the MSIs. There may be an optimization where you can build .wixouts with .wxl files to create localized .wixouts and torch those .wixouts. This will not have the file table information correct so it may not work for you. Also, Peter was talking about issues with torch and .wixouts but I don't remember them right now. It's been a long while since I did all the above so YMMV and please feel free to correct me where I'm wrong. It might be a bug. <smile/> -----Original Message----- From: Neil Sleightholm [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2008 14:19 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Install Localisation I am looking for advise in localising installs. I need to deploy an application in several languages and I thought I had the solution, what I did was this: 1. Set the CAB file as not embedded as the files are the same for all languages. 2. Run candle for wxs files 3. Run light against the wixobj files but specifying a different culture each time I ran it 4. This creates an msi for each language with an external CAB file. This works but I have just noticed a major problem, each time I run light it generates a new product and package code (I use the Guid="*" syntax for them). So this means that each language has a different product/package code and this is clear not really correct. Can anyone suggest a better method for doing this? Ideally I would like to generate one msi and then run some command to generate a transform for each language. Thanks Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
