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
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. smile/
Of course not. I had half guessed it was something like this anyway. I guess
it's a matter
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 processing
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. smile/
Of course not. I had
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 OutputDebugString
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. smile/
-Original Message-
From: John Hall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October
6 matches
Mail list logo
