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
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:
row
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
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
Hi Blair,
1) My team leader found source of trouble, error appear when you add a binary
resource via wix variable like this,
Binary Id=WixUI_Bmp_Banner SourceFile=!(wix.WixUIBannerBmp)/
Currently we aren't using that directly, but it's default included with
WixUI_Common reference (we built UIs
: 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
...@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
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
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
[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
@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
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
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
14 matches
Mail list logo
