[wix-users] Required help in Logging.

[Rob Mensching]

Note: setting that value will log sensitive command-line parameters (such as passwords) and will affect all installs on the machine if it is not removed.

_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Gary M
Sent: Thursday, May 19, 2016 4:14 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Required help in Logging.

I ran into the same issue. The way I solved  it in the past is writing a simple setup.exe that sets the Installer registry debug values and calling msiexe with the logging parameters.

The log's raw aesthetics has "much to be desired" as an end user report.
David Watson's suggestion to use Wilogutl.exe is a good first step. If you want something more user friendly, a parser may be required. What I've also done is custom actions built for generating an  installation report. I never figured out how to "read" the install log in a custom action.

Here is the registry settings I used with the setup.exe approach:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Debug"=dword:00000007