Re: [WiX-users] torch transforms
Sure, Here you are: http://wixtoolset.org/issues/4109/ Best regards, Enrique -Mensaje original- De: Blair Murri [mailto:os...@live.com] Enviado el: sábado, 14 de septiembre de 2013 4:06 Para: General discussion for Windows Installer XML toolset. Asunto: Re: [WiX-users] torch transforms Enrique, Could you do me a favor? When the issues database is back up and running, could you create a feature request as I described it? Thank you,Blair > From: edoming...@goalsystems.com > To: wix-users@lists.sourceforge.net > Date: Thu, 12 Sep 2013 16:05:05 +0200 > Subject: Re: [WiX-users] torch transforms > > Thanks a lot for your assistance. > Best regards, > Enrique Domínguez > > -- > How ServiceNow helps IT people transform IT departments: > 1. Consolidate legacy IT systems to a single system of record for IT > 2. Standardize and globalize service processes across IT 3. Implement > zero-touch automation to replace manual, redundant tasks > http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.c > lktrk ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Enrique, Could you do me a favor? When the issues database is back up and running, could you create a feature request as I described it? Thank you,Blair > From: edoming...@goalsystems.com > To: wix-users@lists.sourceforge.net > Date: Thu, 12 Sep 2013 16:05:05 +0200 > Subject: Re: [WiX-users] torch transforms > > Thanks a lot for your assistance. > Best regards, > Enrique Domínguez > > -- > How ServiceNow helps IT people transform IT departments: > 1. Consolidate legacy IT systems to a single system of record for IT > 2. Standardize and globalize service processes across IT > 3. Implement zero-touch automation to replace manual, redundant tasks > http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Thanks a lot for your assistance. Best regards, Enrique Domínguez -- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Yes, I keep forgetting that WixVariables and binder variables are both resolved in the binder and not the linker. I'm thinking of writing a binder for patching does everything the binder would do except actually assemble the MSI and associated cabs. Then you could melt your baseline MSI, pass wixpdbs to torch, and avoid much of the build slowdown and excess disk space consumption used in generating MSP files today. Then pipeline it into the current .target files and make that one less manual hassle to get to patching. Enrique Domínguez wrote: Hi Blair, 1) My team leader found source of trouble, error appear when you add a binary resource via wix variable like this, Currently we aren't using that directly, but it's default included with WixUI_Common reference (we built UIs over that) Wixout xml part got lines like: !(wix.WixUIUpIco=E:\delivery\Dev\wix36_public\src\ext\UIExtension\wixlib\Bitmaps\up.ico) Temporary solution was including WixUI_Common with hardcoded filepaths in wix project. 2) Another issue we found was building with Msi's and mst's worked fine, but wixouts don't. Torch told us, error TRCH0269: The value '*' is not valid for the ProductCode when used in a transform or in a patch. Copy the ProductCode from your target product MSI into the Product/@Id attribute value for your product authoring. -- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Hi, I come back my project, and trying to apply changes proposed and can't solve it because more exclamation variables, not resolved, being found; now error was, torch.exe(0,0): error TRCH0001: Could not find file '!(bindpath.x86)PrintEula.dll' wixout xml line: WixUIWixca !(bindpath.x86)PrintEula.dll I suspecting exclamation variables didn't resolved in wixout build and it's source of trouble, could somebody confirm if its possible? Thanks a lot. -- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Hi Blair, 1) My team leader found source of trouble, error appear when you add a binary resource via wix variable like this, Currently we aren't using that directly, but it's default included with WixUI_Common reference (we built UIs over that) Wixout xml part got lines like: !(wix.WixUIUpIco=E:\delivery\Dev\wix36_public\src\ext\UIExtension\wixlib\Bitmaps\up.ico) Temporary solution was including WixUI_Common with hardcoded filepaths in wix project. 2) Another issue we found was building with Msi's and mst's worked fine, but wixouts don't. Torch told us, error TRCH0269: The value '*' is not valid for the ProductCode when used in a transform or in a patch. Copy the ProductCode from your target product MSI into the Product/@Id attribute value for your product authoring. -- How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Hi Blair, I'm preparing a test file with as less as possible, in the mean time, I got a different error runing my script as admin. I'm posting here and hope it helps, >> torch.exe : error TRCH0001 : Index and length must refer to a location within the string. Parameter name: length Exception Type: System.ArgumentOutOfRangeException Stack Trace: at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) at System.String.Substring(Int32 startIndex, Int32 length) at Microsoft.Tools.WindowsInstallerXml.Binder.BindTransform(Output transform, String transformFile) at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file ) at Microsoft.Tools.WindowsInstallerXml.Tools.Torch.Run(String[] args) >> -Mensaje original- De: Blair Murri [mailto:os...@live.com] Enviado el: jueves, 22 de agosto de 2013 7:17 Para: General discussion for Windows Installer XML toolset. Asunto: Re: [WiX-users] torch transforms Enrique, Please post a bug with example wxs and wixout files that torch is unable to parse. I would love to look at that and fix it. Blair > Date: Wed, 21 Aug 2013 06:12:04 -0700 > From: timmay...@smarttech.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] torch transforms > > Hello Enrique Domínguez, > > We are basically in the same boat.. We have quite a few WiX projects > that contain between 12 and 18 language cultures and at the moment our > project files are set up to build all cultures and then using the > Torch commands to generate all the language .mst. This process takes > quite a while to complete. > > So if you discover a faster method, that we can automate through our > TeamCity build server, that reduces the time to perform these builds > then let me know. If we can simple build the English msi and then have > all the language .mst generated from that then that would be great and > save quite a lot of times during our builds. > > Thanks. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/torch-tr > ansforms-tp7588172p7588293.html Sent from the wix-users mailing list > archive at Nabble.com. > > -- > Introducing Performance Central, a new site from SourceForge > and AppDynamics. Performance Central is your source for news, > insights, analysis and resources for efficient Application Performance > Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.c > lktrk ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Enrique, Please post a bug with example wxs and wixout files that torch is unable to parse. I would love to look at that and fix it. Blair > Date: Wed, 21 Aug 2013 06:12:04 -0700 > From: timmay...@smarttech.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] torch transforms > > Hello Enrique Domínguez, > > We are basically in the same boat.. We have quite a few WiX projects that > contain between 12 and 18 language cultures and at the moment our project > files are set up to build all cultures and then using the Torch commands to > generate all the language .mst. This process takes quite a while to > complete. > > So if you discover a faster method, that we can automate through our > TeamCity build server, that reduces the time to perform these builds then > let me know. If we can simple build the English msi and then have all the > language .mst generated from that then that would be great and save quite a > lot of times during our builds. > > Thanks. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/torch-transforms-tp7588172p7588293.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Hello Enrique Domínguez, We are basically in the same boat.. We have quite a few WiX projects that contain between 12 and 18 language cultures and at the moment our project files are set up to build all cultures and then using the Torch commands to generate all the language .mst. This process takes quite a while to complete. So if you discover a faster method, that we can automate through our TeamCity build server, that reduces the time to perform these builds then let me know. If we can simple build the English msi and then have all the language .mst generated from that then that would be great and save quite a lot of times during our builds. Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/torch-transforms-tp7588172p7588293.html Sent from the wix-users mailing list archive at Nabble.com. -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] torch transforms
Sorry for my misunderstanding, I have tested same build changing torch input to
all wixout files, as you told me, but I got same behaviour.
torch.exe(0,0): error TRCH0001: The given path's format is not supported.
No idea how to solve it :(
-Mensaje original-
De: Blair Murri [mailto:os...@live.com]
Enviado el: martes, 20 de agosto de 2013 21:00
Para: General discussion for Windows Installer XML toolset.
Asunto: Re: [WiX-users] torch transforms
Your already building an MSI. I'm saying you still build that same just-one
MSI, but in a slightly more indirect way. If you want to create MSTs using
wixouts instead of wixpdbs you need a wixout from your base also, not its
wixpdb. I was simply describing how to get a wixout from your base.
Yes, you can get those MSTs from torch. You don't need to build actual MSIs
from all of your cultures, only from your base. I'm trying to tell you an
alternate way to build your base MSI so that you will have files that torch can
use together.
> From: edoming...@goalsystems.com
> To: wix-users@lists.sourceforge.net
> Date: Tue, 20 Aug 2013 10:58:13 +0200
> Subject: Re: [WiX-users] torch transforms
>
> Thansk for your reply, but I don't like to build MSIs but MSTs. I only
> needing en-US MSI (neutral) and MSTs from other cultures. It's for building a
> Multilanguage MSI (all in one) Can't get I those MSTs with torch then?
>
>
> Enrique Domínguez Pinos
>
> -Mensaje original-
> De: Blair Murri [mailto:os...@live.com] Enviado el: lunes, 19 de
> agosto de 2013 18:12
> Para: General discussion for Windows Installer XML toolset.
> Asunto: Re: [WiX-users] torch transforms
>
> Torch requires that its inputs all be in the same format. Create all of your
> MSIs in WIXOUT, then run your base through light again to generate that MSI.
> Pass only WIXOUTs to torch.
>
> > From: edoming...@goalsystems.com
> > To: wix-users@lists.sourceforge.net
> > Date: Mon, 19 Aug 2013 12:14:21 +0200
> > Subject: [WiX-users] torch transforms
> >
> > Hi all,
> > I'm building a multilanguage msi; for doing that I'm generating all msi
> > cultures I need and then getting msts using torch. My msi it's big and
> > making all cultures it's slow so I thinking build first base msi ('neutral'
> > lang as en-US) and doing all others as wixout like this (showing spanish)
> > "C:\Program Files (x86)\WiX Toolset v3.6\bin"\Light.exe
> > -nologo -out ..\x86\Release\es-ES\AcmeApp_Setup.wixout -xo -cultures:es-ES
> > -ext "C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixUIExtension.dll -ext
> > "C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixNetFxExtension.dll
> > -sice:ICE30 -sice:ICE61 -sice:ICE09 -reusecab -cc .\CABsCache
> > "obj\x86\Release\*.wixobj"
> > C:\Proyectos\App\WiX_Installer\\SetupLibrary\bin\x86\Release\SetupLibrary.wixlib
> > C:\Proyectos\App\WiX_Installer\\SetupUI\bin\x86\Release\SetupUI.wixlib
> > "C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch -nologo
> > -xi -val g ..\x86\Release\en-US\AcmeApp_Setup.wixpdb
> > ..\x86\Release\es-ES\AcmeApp_Setup.wixout -out
> > transforms\AcmeApp_Setup_es-ES.wixout
> > "C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch
> > -nologo
> > C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Set
> > up
> > _es-ES.wixout -out
> > C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Set
> > up
> > _es-ES.mst
> > torch.exe(0,0): error TRCH0001: The given path's format is not supported.
> > Exception Type: System.NotSupportedException
> > Stack Trace:
> > at
> > System.Security.Util.StringExpressionSet.CanonicalizePath(String path,
> > Boolean needFullPath)
> > at
> > System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[]
> > str, Boolean needFullPath)
> > at
> > System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess
> > access, AccessControlActions control, String[] pathListOrig, Boolean
> > checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
> > at
> > System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess
> > access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
> > at System.IO.FileInfo.Init(String fileName, Boolean
> > checkHost)
> > at System.IO.FileInfo..ctor(String fileName)
> > at
> > Microsoft.Tools.WindowsIns
Re: [WiX-users] torch transforms
Your already building an MSI. I'm saying you still build that same just-one
MSI, but in a slightly more indirect way. If you want to create MSTs using
wixouts instead of wixpdbs you need a wixout from your base also, not its
wixpdb. I was simply describing how to get a wixout from your base.
Yes, you can get those MSTs from torch. You don't need to build actual MSIs
from all of your cultures, only from your base. I'm trying to tell you an
alternate way to build your base MSI so that you will have files that torch can
use together.
> From: edoming...@goalsystems.com
> To: wix-users@lists.sourceforge.net
> Date: Tue, 20 Aug 2013 10:58:13 +0200
> Subject: Re: [WiX-users] torch transforms
>
> Thansk for your reply, but I don't like to build MSIs but MSTs. I only
> needing en-US MSI (neutral) and MSTs from other cultures. It's for building a
> Multilanguage MSI (all in one)
> Can't get I those MSTs with torch then?
>
>
> Enrique Domínguez Pinos
>
> -Mensaje original-
> De: Blair Murri [mailto:os...@live.com]
> Enviado el: lunes, 19 de agosto de 2013 18:12
> Para: General discussion for Windows Installer XML toolset.
> Asunto: Re: [WiX-users] torch transforms
>
> Torch requires that its inputs all be in the same format. Create all of your
> MSIs in WIXOUT, then run your base through light again to generate that MSI.
> Pass only WIXOUTs to torch.
>
> > From: edoming...@goalsystems.com
> > To: wix-users@lists.sourceforge.net
> > Date: Mon, 19 Aug 2013 12:14:21 +0200
> > Subject: [WiX-users] torch transforms
> >
> > Hi all,
> > I'm building a multilanguage msi; for doing that I'm generating all msi
> > cultures I need and then getting msts using torch. My msi it's big and
> > making all cultures it's slow so I thinking build first base msi ('neutral'
> > lang as en-US) and doing all others as wixout like this (showing spanish)
> > "C:\Program Files (x86)\WiX Toolset v3.6\bin"\Light.exe
> > -nologo -out ..\x86\Release\es-ES\AcmeApp_Setup.wixout -xo -cultures:es-ES
> > -ext "C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixUIExtension.dll -ext
> > "C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixNetFxExtension.dll
> > -sice:ICE30 -sice:ICE61 -sice:ICE09 -reusecab -cc .\CABsCache
> > "obj\x86\Release\*.wixobj"
> > C:\Proyectos\App\WiX_Installer\\SetupLibrary\bin\x86\Release\SetupLibrary.wixlib
> > C:\Proyectos\App\WiX_Installer\\SetupUI\bin\x86\Release\SetupUI.wixlib
> > "C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch -nologo
> > -xi -val g ..\x86\Release\en-US\AcmeApp_Setup.wixpdb
> > ..\x86\Release\es-ES\AcmeApp_Setup.wixout -out
> > transforms\AcmeApp_Setup_es-ES.wixout
> > "C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch
> > -nologo
> > C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Setup
> > _es-ES.wixout -out
> > C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Setup
> > _es-ES.mst
> > torch.exe(0,0): error TRCH0001: The given path's format is not supported.
> > Exception Type: System.NotSupportedException
> > Stack Trace:
> > at
> > System.Security.Util.StringExpressionSet.CanonicalizePath(String path,
> > Boolean needFullPath)
> > at
> > System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[]
> > str, Boolean needFullPath)
> > at
> > System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess
> > access, AccessControlActions control, String[] pathListOrig, Boolean
> > checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
> > at
> > System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess
> > access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
> > at System.IO.FileInfo.Init(String fileName, Boolean
> > checkHost)
> > at System.IO.FileInfo..ctor(String fileName)
> > at
> > Microsoft.Tools.WindowsInstallerXml.BinderFileManager.CompareFiles(String
> > targetFile, String updatedFile)
> > at
> > Microsoft.Tools.WindowsInstallerXml.Binder.BindTransform(Output transform,
> > String transformFile)
> > at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output
> > output, String file)
> > at
> > Microsoft.Tools.WindowsIn
Re: [WiX-users] torch transforms
Thansk for your reply, but I don't like to build MSIs but MSTs. I only needing
en-US MSI (neutral) and MSTs from other cultures. It's for building a
Multilanguage MSI (all in one)
Can't get I those MSTs with torch then?
Enrique Domínguez Pinos
-Mensaje original-
De: Blair Murri [mailto:os...@live.com]
Enviado el: lunes, 19 de agosto de 2013 18:12
Para: General discussion for Windows Installer XML toolset.
Asunto: Re: [WiX-users] torch transforms
Torch requires that its inputs all be in the same format. Create all of your
MSIs in WIXOUT, then run your base through light again to generate that MSI.
Pass only WIXOUTs to torch.
> From: edoming...@goalsystems.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 12:14:21 +0200
> Subject: [WiX-users] torch transforms
>
> Hi all,
> I'm building a multilanguage msi; for doing that I'm generating all msi
> cultures I need and then getting msts using torch. My msi it's big and making
> all cultures it's slow so I thinking build first base msi ('neutral' lang as
> en-US) and doing all others as wixout like this (showing spanish)
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\Light.exe -nologo
> -out ..\x86\Release\es-ES\AcmeApp_Setup.wixout -xo -cultures:es-ES -ext
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixUIExtension.dll -ext
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixNetFxExtension.dll
> -sice:ICE30 -sice:ICE61 -sice:ICE09 -reusecab -cc .\CABsCache
> "obj\x86\Release\*.wixobj"
> C:\Proyectos\App\WiX_Installer\\SetupLibrary\bin\x86\Release\SetupLibrary.wixlib
> C:\Proyectos\App\WiX_Installer\\SetupUI\bin\x86\Release\SetupUI.wixlib
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch -nologo -xi
> -val g ..\x86\Release\en-US\AcmeApp_Setup.wixpdb
> ..\x86\Release\es-ES\AcmeApp_Setup.wixout -out
> transforms\AcmeApp_Setup_es-ES.wixout
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch
> -nologo
> C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Setup
> _es-ES.wixout -out
> C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Setup
> _es-ES.mst
> torch.exe(0,0): error TRCH0001: The given path's format is not supported.
> Exception Type: System.NotSupportedException
> Stack Trace:
> at
> System.Security.Util.StringExpressionSet.CanonicalizePath(String path,
> Boolean needFullPath)
> at
> System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[]
> str, Boolean needFullPath)
> at
> System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess
> access, AccessControlActions control, String[] pathListOrig, Boolean
> checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
> at
> System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess
> access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
> at System.IO.FileInfo.Init(String fileName, Boolean checkHost)
> at System.IO.FileInfo..ctor(String fileName)
> at
> Microsoft.Tools.WindowsInstallerXml.BinderFileManager.CompareFiles(String
> targetFile, String updatedFile)
> at
> Microsoft.Tools.WindowsInstallerXml.Binder.BindTransform(Output transform,
> String transformFile)
> at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output
> output, String file)
> at
> Microsoft.Tools.WindowsInstallerXml.Tools.Torch.Run(String[] args)
> Binder temporary directory located at
> 'C:\Users\edominguez\AppData\Local\Temp\p2vvirxq'.
> Unbinder temporary directory located at
> 'C:\Users\edominguez\AppData\Local\Temp\p2vvirxq'.
> Torch temporary directory located at
> 'C:\Users\edominguez\AppData\Local\Temp\ll1p1c42'.
> Last torch line should give me transforms in mst format, no matter how I
> change paths. Maybe it could be accomplished in less commands?
>
> Thanks!!
> --
> Get 100% visibility into Java/.NET code with AppDynamics
> Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.c
> lktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sou
Re: [WiX-users] torch transforms
Torch requires that its inputs all be in the same format. Create all of your
MSIs in WIXOUT, then run your base through light again to generate that MSI.
Pass only WIXOUTs to torch.
> From: edoming...@goalsystems.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 12:14:21 +0200
> Subject: [WiX-users] torch transforms
>
> Hi all,
> I'm building a multilanguage msi; for doing that I'm generating all msi
> cultures I need and then getting msts using torch. My msi it's big and making
> all cultures it's slow so I thinking build first base msi ('neutral' lang as
> en-US) and doing all others as wixout like this (showing spanish)
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\Light.exe -nologo
> -out ..\x86\Release\es-ES\AcmeApp_Setup.wixout -xo -cultures:es-ES -ext
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixUIExtension.dll -ext
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixNetFxExtension.dll
> -sice:ICE30 -sice:ICE61 -sice:ICE09 -reusecab -cc .\CABsCache
> "obj\x86\Release\*.wixobj"
> C:\Proyectos\App\WiX_Installer\\SetupLibrary\bin\x86\Release\SetupLibrary.wixlib
> C:\Proyectos\App\WiX_Installer\\SetupUI\bin\x86\Release\SetupUI.wixlib
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch -nologo -xi
> -val g ..\x86\Release\en-US\AcmeApp_Setup.wixpdb
> ..\x86\Release\es-ES\AcmeApp_Setup.wixout -out
> transforms\AcmeApp_Setup_es-ES.wixout
> "C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch -nologo
> C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Setup_es-ES.wixout
> -out
> C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Setup_es-ES.mst
> torch.exe(0,0): error TRCH0001: The given path's format is not supported.
> Exception Type: System.NotSupportedException
> Stack Trace:
> at
> System.Security.Util.StringExpressionSet.CanonicalizePath(String path,
> Boolean needFullPath)
> at
> System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[]
> str, Boolean needFullPath)
> at
> System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess
> access, AccessControlActions control, String[] pathListOrig, Boolean
> checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
> at
> System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess
> access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
> at System.IO.FileInfo.Init(String fileName, Boolean checkHost)
> at System.IO.FileInfo..ctor(String fileName)
> at
> Microsoft.Tools.WindowsInstallerXml.BinderFileManager.CompareFiles(String
> targetFile, String updatedFile)
> at
> Microsoft.Tools.WindowsInstallerXml.Binder.BindTransform(Output transform,
> String transformFile)
> at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output
> output, String file)
> at
> Microsoft.Tools.WindowsInstallerXml.Tools.Torch.Run(String[] args)
> Binder temporary directory located at
> 'C:\Users\edominguez\AppData\Local\Temp\p2vvirxq'.
> Unbinder temporary directory located at
> 'C:\Users\edominguez\AppData\Local\Temp\p2vvirxq'.
> Torch temporary directory located at
> 'C:\Users\edominguez\AppData\Local\Temp\ll1p1c42'.
> Last torch line should give me transforms in mst format, no matter how I
> change paths. Maybe it could be accomplished in less commands?
>
> Thanks!!
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] torch transforms
Hi all,
I'm building a multilanguage msi; for doing that I'm generating all msi
cultures I need and then getting msts using torch. My msi it's big and making
all cultures it's slow so I thinking build first base msi ('neutral' lang as
en-US) and doing all others as wixout like this (showing spanish)
"C:\Program Files (x86)\WiX Toolset v3.6\bin"\Light.exe -nologo
-out ..\x86\Release\es-ES\AcmeApp_Setup.wixout -xo -cultures:es-ES -ext
"C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixUIExtension.dll -ext
"C:\Program Files (x86)\WiX Toolset v3.6\bin"\WixNetFxExtension.dll -sice:ICE30
-sice:ICE61 -sice:ICE09 -reusecab -cc .\CABsCache "obj\x86\Release\*.wixobj"
C:\Proyectos\App\WiX_Installer\\SetupLibrary\bin\x86\Release\SetupLibrary.wixlib
C:\Proyectos\App\WiX_Installer\\SetupUI\bin\x86\Release\SetupUI.wixlib
"C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch -nologo -xi
-val g ..\x86\Release\en-US\AcmeApp_Setup.wixpdb
..\x86\Release\es-ES\AcmeApp_Setup.wixout -out
transforms\AcmeApp_Setup_es-ES.wixout
"C:\Program Files (x86)\WiX Toolset v3.6\bin"\torch -nologo
C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Setup_es-ES.wixout
-out
C:\Proyectos\App\WiX_Installer\\AcmeApp_Setup\transforms\AcmeApp_Setup_es-ES.mst
torch.exe(0,0): error TRCH0001: The given path's format is not supported.
Exception Type: System.NotSupportedException
Stack Trace:
at
System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean
needFullPath)
at
System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[]
str, Boolean needFullPath)
at
System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess
access, AccessControlActions control, String[] pathListOrig, Boolean
checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
at
System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess
access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
at System.IO.FileInfo.Init(String fileName, Boolean checkHost)
at System.IO.FileInfo..ctor(String fileName)
at
Microsoft.Tools.WindowsInstallerXml.BinderFileManager.CompareFiles(String
targetFile, String updatedFile)
at
Microsoft.Tools.WindowsInstallerXml.Binder.BindTransform(Output transform,
String transformFile)
at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output
output, String file)
at Microsoft.Tools.WindowsInstallerXml.Tools.Torch.Run(String[]
args)
Binder temporary directory located at
'C:\Users\edominguez\AppData\Local\Temp\p2vvirxq'.
Unbinder temporary directory located at
'C:\Users\edominguez\AppData\Local\Temp\p2vvirxq'.
Torch temporary directory located at
'C:\Users\edominguez\AppData\Local\Temp\ll1p1c42'.
Last torch line should give me transforms in mst format, no matter how I change
paths. Maybe it could be accomplished in less commands?
Thanks!!
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
