Any Ideas on that? 2014-08-29 16:11 GMT+02:00 Tobias S <tobias.s1...@gmail.com>:
> Hi all, > > Goal is to build the language transforms (mst files) based upon the wixout > files instead the MSIs to drastically reduce build time. > > I read > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/torch-transforms-td7588172.html > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Building-localized-versions-of-an-installer-td710501.html#a710505 > > For simplification a simple sample: we want a german mst using wix3.6. > > In my understanding it works like following: > 1. light to generate wixout files for all lanugages (e.g. en-us.wixout, > de-de.wixout) > 2. torch to create wixmst file as diff between the 2 wixout files > 3. torch to create mst based on wixmst and ??? > > Now I'm struggling with the correct command line syntax for that. > For 1. I assume just using the -xo should be ok > For 2. > torch.exe -t language -v -p -xi -xo en-US\MstPerformanceTesting.wixout > de-de\MstPerformanceTesting.wixout -out en-US\MstPerformanceTesting.wixmst > For 3. > torch.exe" "en-US\MstPerformanceTesting.wixmst" -out > en-US\MstPerformanceTesting.mst > > results in a > torch.exe : error TRCH0001 : The given path's format is not supported. > > Exception Type: System.NotSupportedException > > Is the syntax / approach correct? > Am I struggling with bugs in WiX 3.6? Or with something else? > > Thanks and best regards, > Tobias > ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
