Mark Allanson wrote: > Just wondering how I can go about enabling trace from WiX custom > actions. The perf counter install is failing without letting me know > why (other than the standard windows installer error 1723, a DLL count > not be run). I have had a look through the wix CA code, and can see it > uses standard OutputDebugStringA, but can't see any trace output.
Only debug builds of WiX/wcautil use OutputDebugString. Otherwise, wcautil detects verbose logging and will write those messages to the MSI log. MSI doesn't expose what kind of logging is enabled, so wcautil first checks for a LOGVERBOSE property being set; if not, it checks the MSI logging policy registry at HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer!Logging to see if it includes the "v" switch. In very recent builds, I added a check for the standard MSI property MsiLogging (in MSI 4.0 on Vista) too. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
