Thank-you , Rob and Josh. That looks like it should work, but it fails with a not-very-helpful error message:
I have produced a ".wixmst" file from torch like so: Ø torch.exe -t language -v -p -xi -xo C:\eao neutral.wixout en-us.wixout -out en-us.wixmst Now call light on the wixmst file to create the transform: Ø light.exe en-us.wixmst Microsoft (R) Windows Installer Xml Linker version 3.0.3907.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. C:\Documents and Settings\jamesf\Local Settings\Temp\ail5es2w\File.idt : error LGHT0136 : There was an error importing table 'File' from this file. Binder temporary directory located at 'C:\Documents and Settings\jamesf\Local Settings\Temp\ail5es2w'. Validator temporary directory located at 'C:\Documents and Settings\jamesf\Local Settings\Temp\ihybiq-8'. I will debug this further, but before I do, is there something obvious that I'm doing wrong? From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, May 15, 2008 2:01 PM To: Fairweather, James; wix-users@lists.sourceforge.net Subject: RE: Building localized versions of an installer You're right on track. Last step is to take the .wixout (should have been named ".wixmsi" to match the other things but .wixout came first) and feed it back into light.exe. Light will finish processing the .wixout into MSI. Is that detailed enough or am I missing a step? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fairweather, James Sent: Thursday, May 15, 2008 13:12 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Building localized versions of an installer Many of our companies' products are localized into several languages. To build the an installer to handle this, we first build a "neutral" MSI, then for each culture, we build an MSI, then use msitran to build a transform, and finally msidb to merge the transform back to the neutral MSI. This works, but it's really slow because of all the file copying and cabinet building. The fileset is the same for all cultures, so it would be really handy if there were a way to tell light to not build the cabinet file (after the first one). There is a -reusecab option, but it's still pretty slow (I think due to a lot of file copying), and it sometimes crashes on large filesets. The approach we are exploring is to use the XML format (-xo option to light), then use the torch tool to build the transform from that. While this is great from a speed point of view, I don't see a way of getting from the XML format back to MSI/MST. Am I missing something, or has that simply not been implemented to date? James Fairweather Lead developer and support engineer Core Team 604.456.3911 (x13911) <http://eatech.ea.com/>
<<image001.jpg>>
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
