I set the environment variable MsiBreak for native code ( http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx ) and MMsiBreak for managed code ( http://blog.torresdal.net/2008/10/26/WiXAndDTFDebugAManagedCustomActionAndHowToGenerateAnMSILog.aspx http://blog.torresdal.net/2008/10/26/WiXAndDTFDebugAManagedCustomActionAndHowToGenerateAnMSILog.aspx ) to the name of the custom action to debug. This way you don't have to mess with adding message boxes.
As was already mentioned, sometimes setting environment variables doesn't work until you reboot so what I do is launch a command prompt, set the variable (using the SET command), then launch the install from the command prompt (this always works for me). -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-debug-CustomAction-DLL-tp5458781p5462437.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
