WcaLog just calls MSI APIs. You might try debugging down to see if the MSI
API calls are return failures.

I've never seen a problem with logging except that you can't log at all from
a button push.

On Wed, Jul 21, 2010 at 1:05 PM, Fangren <tim.kr...@shavlik.com> wrote:

>
> I have a custom action that does not log no matter what method is used to
> turn logging on.  Even though it executes correctly.  I can see the
> property
> being set in the log and the custom action begin and end.
>
> Code example (made generic):
>
> extern "C" UINT __stdcall MyCustomAction(MSIHANDLE install)
> {
>        CUSTOM_ACTION_BEGIN
>        {
>                HRESULT hr = ::WcaInitialize(install, "MyCustomAction");
>                if (FAILED(hr))
>                {
>                        return ERROR_INSTALL_FAILURE;
>                }
>
>                ::WcaLog(LOGMSG_STANDARD, "Establishing MyCustomAction");
>
>                std::wstring info = GenerateInfo();
>                SaveMsiProperty(install, L"REGISTEREDINFO", info);
>
>                ::WcaLog(LOGMSG_VERBOSE, "Info is %S", info);
>
>                return ::WcaFinalize(ERROR_SUCCESS);
>        }
>        CUSTOM_ACTION_END
> }
>
>
> Based on research it appears there is a bug in wcautil that prevent
> deferred
> custom actions from logging.  Looking into this I found the following:
>
> http://www.joyofsetup.com/2008/07/15/verbose-logging-from-wcautil/
> In the comments is the mention of a bug being created in 2008.
>
> I did find a similar bug on SouceForge: ID 1845036.
>
> https://sourceforge.net/tracker/index.php?func=detail&aid=1845036&group_id=105970&atid=642714
>
> This bug was closed because they weren't sure how to reproduce it.  I have
> been able to consistently reproduce this through use of deferred custom
> actions.  Logging works as expected in my non-deferred custom actions.
>
> Does anyone know if this has been fixed yet?  If not is there a method to
> re-open the bug or should I submit a new one?
>
> I did try this in a 3.5 based build and the same problem still existed.
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wcalog-does-not-log-tp5322711p5322711.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to