In article <1242174267154-2877231.p...@n2.nabble.com>,
achandrapano <achan...@panologic.com> writes:
> So it looks like all the 3 conditions are evaluating to true, but nothing
> happens. Is there any way to debug what the error really is? The Msi log
> shows nothing to help me besides those two lines above, then it moves to the
> next rollback action which is Removing shortcuts.
Ah, the reason your message box didn't appear is because you attempted
to display a message box from inside the server process, which isn't
attached to your desktop. Instead of calling ::MessageBox, call
::MsiProcessMessage. This will cause a message box to be displayed
back on the client side from the server. It is the client that has
the GUI.
You can also use MsiProcessMessage to write debugging information to
the log.
One technique people use for debugging CA's is to use the message box
to block the execution so that you can attach a debugger to the
process and step through your code. I've never tried that technique,
I've always debugged my CA's with unit tests before deploying them and
if I had a problem during deployment, I used MsiProcessMessage and the
log file to figure it out.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
