> If you're looking for a quick non-debugger method, property
> changes are still logged. It may be a hack, but calling
> MsiSetProperty(hMSI, _T("LOGME"), _T("...")) is effective.
Michael,
That's a nice workaround - I like it.
Cheers,
John
--
In article <[EMAIL PROTECTED]>,
"Michael Urman" <[EMAIL PROTECTED]> writes:
> If you're looking for a quick non-debugger method, property changes
> are still logged. It may be a hack, but calling MsiSetProperty(hMSI,
> _T("LOGME"), _T("...")) is effective.
Another option is to call OutputDe
On Thu, Oct 2, 2008 at 3:13 AM, John Hall
<[EMAIL PROTECTED]> wrote:
>> Yeah, Windows Installer doesn't let it work. Why? Some
>> message processing issue inside them. I think this is
>> documented in some small print somewhere.
>>
>> PS: Please don't shoot the messenger.
>
> Of course not. I
This is how I generally do it (message box/attach debugger) -- although
you can of course do your own logging.
You could probably even trigger it off of a property passed on the
MSIEXEC command line.
John Hall wrote:
>> Yeah, Windows Installer doesn't let it work. Why? Some
>> message process
> Yeah, Windows Installer doesn't let it work. Why? Some
> message processing issue inside them. I think this is
> documented in some small print somewhere.
>
> PS: Please don't shoot the messenger.
Of course not. I had half guessed it was something like this anyway. I guess
it's a matter o
October 01, 2008 02:05
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Logging from a Custom Action during the UI phase
In my installer I have some C++ custom actions that log to the main MSI log
file using MsiProcessMessage. I'm now writing a CA that is execu
In my installer I have some C++ custom actions that log to the main MSI log
file using MsiProcessMessage. I'm now writing a CA that is executed on a button
press in the UI as the user leaves the feature selection dialog. However, none
of my debug output is appearing in the log.
Is there a reaso
7 matches
Mail list logo
