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

Reply via email to