Thanks Phil, I appreciate that piece of info... Maybe I can use the "Message
Method" to work around this limitation...
http://msdn.microsoft.com/en-us/library/aa368322(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa368322(VS.85).aspx
--
View this message in context:
http://windows-i
sday, June 22, 2010 7:18 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Unable to log through DLL using MsiProcessMessage
By the way - is this DoAction limitation documented somewhere? It's really
too bad this doesn't work ... waah! (Ok, done whining)...
--
View thi
By the way - is this DoAction limitation documented somewhere? It's really
too bad this doesn't work ... waah! (Ok, done whining)...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-log-through-DLL-using-MsiProcessMessage-tp709471p5208982
Yes, that seems to be the case. Any logging I try to do that works, is in a
custom action, not a DoAction event. The ones that fail are in DoAction
events.
Hmmm. I guess I'll have to keep that in mind.
Thanks for demystifying...
--
View this message in context:
http://windows-installer-
ML toolset.
Subject: Re: [WiX-users] Unable to log through DLL using MsiProcessMessage
Ahh... that sounds more a setup design problem ;)
I'm pretty sure I saw a thread recently about strange behaviour when
displaying additional InstallUISequence dialogs for configuration
after InstallExec
Well, I can't support quiet mode using this installer, partially because of
these bad design decisions, and partially because it wasn't in the original
design and I'm a noob.
I should blog about my experience in the WiX world - it has been a little
confusing, to say the least. It might help othe
Ahh... that sounds more a setup design problem ;)
I'm pretty sure I saw a thread recently about strange behaviour when
displaying additional InstallUISequence dialogs for configuration
after InstallExecuteSequence has completed. Sounds similar...
In my opinion you should gather configuration info
Hi Sascha - Thanks for the example code.
I understand the out-of-scope handle problem, and I don't save one and use
it for something...I just mentioned that in the previous post to see if it
made a difference during debug.
My code does work, until after install. I can log all day, but not aft
I'm using the following code (Sample code I found, not originally
written by me) which I haven't had any problems with. According to
msi.chm PMSIHANDLE objects are automatically closed as they go out of
scope, which doesn't happen for MSIHANDLE -- if you're using
MSIHANDLE you're required to close
Thanks for the reply, Blair.
Yeah, I just tried that for the heck of it... I would not ever do that in
production...
But the problem remains... I cannot log something late in the install
process...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.co
ry to respect the above rule.
-Original Message-
From: gapearce [mailto:mr_gapea...@yahoo.com]
Sent: Wednesday, June 16, 2010 11:20 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Unable to log through DLL using MsiProcessMessage
I have a similar problem, and I see
I have a similar problem, and I see this message was ignored by the
community. Maybe it is a stupid question? I dunno - but I have the problem
too.
I noticed my MSIHANDLE is one ('1') before installation of the files. AFter
the files are installed, the MSIHANDLE is eight ('8').
Before install
Hi,
I have a custom action DLL. This DLL has some WinAPI calls and if any error
comes I want to log it to msi logs. Following is the sample code I am using.
rc =
MsiEnableLog(INSTALLLOGMODE_VERBOSE,L"C:\\log.txt",INSTALLLOGATTRIBUTES_APPEND);
if(rc != ERROR_SUCCESS )
::MessageBox(NULL, L"Ms
13 matches
Mail list logo
