No. Burn always logs verbose.
On Tue, Mar 20, 2012 at 8:37 AM, James Green wrote:
> Hi All,
>
> Is there an equivalent logging command for bundles as there is for MSI
> files?
>
> msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log"
>
> Cheers,
>
> James
> LEGAL NOTICE
> This message i
Hi All,
Is there an equivalent logging command for bundles as there is for MSI files?
msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log"
Cheers,
James
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may
contain confidential and / or privileged
Installer XML toolset.
Subject: Re: [WiX-users] verbose
OK, well sort of...I had the wrong Configuration and Platform selected.
Now I see "-v" on the candle and light command line. But, not seeing
any more info than not verbose. I guess I am not quite sure what to
expect here.
---
n...@ophir-spiricon.com]
Sent: Tuesday, August 24, 2010 8:32 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] verbose
For some unknown reason I am getting the wrong assembly into my MSI when
the solution is built on my Team Foundation Server (TFS) build agent.
To resolve this problem I wou
For some unknown reason I am getting the wrong assembly into my MSI when
the solution is built on my Team Foundation Server (TFS) build agent.
To resolve this problem I would like to get a complete list of the files
that are going into the MSI. I tried adding "-v" to the Compiler and
Linker Tool S
I ran into an interesting problem with the log files generated by my
installer.
I have an installer that creates a database and then runs some SQL files to
build the tables, populate them and create procedures. In the SQL scripts,
all database names, table names, column names and owner names are s
6 matches
Mail list logo