> Date: Thu, 11 Dec 2008 15:49:45 -0700 > From: Richard <legal...@xmission.com> > Subject: Re: [WiX-users] CA called from DoAction > >> "The context/handle is different from within DoAction ControlEvent >> rather then sequenced CA. MsiProcessMessage calls won't work." >> My testing confirms this. Is there any reasonable >> (not "an async CA using an RPC mechanism") way to do >> this check during the UI phase of install? >> Right now, I put my CA early in InstallExecuteSequence, >> but this is pretty ugly. > > I'm confused by your question because MsiProcessMessage doesn't > do any checking of anything. It just writes to the log or > displays message boxes.
Thanks for your reply Richard. Sorry, I was just quoting the thread on this list; http://tinyurl.com/6ovukx I have a custom dialog and when I press "Next", I want a custom action to fire to check a value in an edit box. If the CA detects an error, I want it to display a dialog (which does not work apparently due to the communication issue with MsiProcessMessage) and then set "something" (which also apparently does not work) so the original dialog is re-displayed (not moving to the next dialog). Thanks, Dale ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
