OK. That's kinda cool, now how do I stop it from outputting that? :)
From: Bob Arnson [b...@joyofsetup.com]
Sent: June 9, 2014 6:24 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bug in torch - wixmst output is not in XML format
O
On 6/9/2014 9:06 AM, Tunney, Stephen wrote:
> It might be a case of "The Mondays" but I'm at a loss at what you are getting
> at :( What are these other files that might get output by torch? How can I
> supress their output?
Rename the .wixmst to .cab and open it in explorer. You'll see binarie
etup.com]
Sent: June-08-14 10:37 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bug in torch - wixmst output is not in XML format
On 6/8/2014 11:13 AM, Tunney, Stephen wrote:
> Re: [WiX-users] Bug in torch - wixmst output is not in XML format
-xo doesn't produce a text fil
On 6/8/2014 11:13 AM, Tunney, Stephen wrote:
> Re: [WiX-users] Bug in torch - wixmst output is not in XML format
-xo doesn't produce a text file if there are files in the output (which
is pretty often).
--
sig://boB
http://joyofs
Hey everyone,
I've got the following command line for torch after applying melt to a
WiX-built MSI. It is a fairly large MSI (500 megs with cabs embedded).
Starting 'C:\Program Files (x86)\WiX Toolset v3.8\bin\torch.exe -nologo -p -xo
-xi "C:\dev/out/Patch/RTM/Melted/MyMSI.x64/wixpdb/MyMSI.x64.
xes/vsi/solution/components/integrations/obj/wix/ja-jp] info.exe
>> MKS_VS_Integration.msi /d
>> String ID size: 2
>> Code page: 932
>>
>>
>> > -Original Message-
>> > From: Heath Stewart [mailto:clubs...@gmail.com]
>> > Sent: Jun
xe
> MKS_VS_Integration.msi /d
> String ID size: 2
> Code page: 932
>
>
> > -Original Message-
> > From: Heath Stewart [mailto:clubs...@gmail.com]
> > Sent: June 4, 2009 8:43 PM
> > To: General discussion for Windows Installer XML toolset.
> > S
l discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bug in Torch?
>
> Gilad, I need the database code page. The code page shown
> there is only for the summary information stream. The
> database code page can be displayed by running "msiinfo */d*
>
.0.5217.0)
> [19][/u] Security = 2
>
> > -Original Message-
> > From: Heath Stewart [mailto:clubs...@gmail.com]
> > Sent: June 3, 2009 11:07 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Bug in Torch?
> &g
gt; To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bug in Torch?
>
> Gilad, could you detail what the database code pages are set
> to? From the Windows Installer SDK, you can use msiinfo /d
> *msifilename* to retrieve the database code page (n
ixtoolset.org]
> > Sent: June 3, 2009 6:05 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Bug in Torch?
> >
> > Never heard of it. Can you please post a bug and include all
> > of the Property.idt files from the
; Subject: Re: [WiX-users] Bug in Torch?
>
> Never heard of it. Can you please post a bug and include all
> of the Property.idt files from the directories listed below.
>
> Gilad Israeli wrote:
> > Hello
> > I was trying to create a single language msi (for English &
Never heard of it. Can you please post a bug and include all of the
Property.idt files from the directories listed below.
Gilad Israeli wrote:
> Hello
> I was trying to create a single language msi (for English & Japanese). Both
> compiled successfully with candle & light but I ran into the foll
Hello
I was trying to create a single language msi (for English & Japanese). Both
compiled successfully with candle & light but I ran into the following problem
when I ran torch to get the difference between the msi files.
Running torch with the following parameters:
torch.exe -t language
c:/s
14 matches
Mail list logo