It's just scheduled and not a specific response to user action. It executes
when the user clicks next the first time.
...
...
-Tim
On Mon, Jul 26, 2010 at 2:18 PM, MikeR wrote:
>
> How is your custom action being called? As Rob said if it's off a push
> button, or launched through a
How is your custom action being called? As Rob said if it's off a push
button, or launched through any MSI UI via a DoAction control event logging
will not occur. This is a limitation of Windows Installer, it's documented
somewhere in the SDK, I forget where. If your custom action is scheduled
I took the msi call code out of wcautil and called it manually without
without the checks for log level.
Using the log command directly from wcalog.cpp
MsiProcessMessage(install, INSTALLMESSAGE_INFO, hrec); returns 0 creating
no output
Modifying it to try and force logging
MsiProcessMessage(inst
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 wrote:
>
> I have a custom action that does not log no m
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
5 matches
Mail list logo
