Bugs item #1845036, was opened at 2007-12-05 10:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1845036&group_id=105970
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: extensions
Group: v3.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Eric Bickle (shadowchaser)
Assigned to: Scott Kurtzeborn (scotk)
Summary: WcaLog does not log
Initial Comment:
Calling WcaLog from a custom action never logs to the MSI log file.
For example:
extern "C" UINT __stdcall Test(__in MSIHANDLE hInstall)
{
HRESULT hr = S_OK;
hr = WcaInitialize(hInstall, "Test");
ExitOnFailure(hr, "Failed to initialize."
WcaLog(LOGMSG_STANDARD, "Never appears in log");
LExit:
return WcaFinalize(SUCCEEDED(hr) ? ERROR_SUCCESS : ERROR_INSTALL_FAILURE);
}
Invoking MSI exec with logging never logs the message to the log file,
regardless of the setting.
msiexec /i Test.msi /lv VerboseLog.txt
VerboseLog.txt is created and contains lines written by MSI showing that the
custom action is being invoked. None of the WcaLog commands write to the log
file.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1845036&group_id=105970
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
