Throw a WixException is one way (requires creating/obtaining a WixErrorEventArgs object which can be generated by compiling a file similar to the messages.xml files in the wix toolset). Some of the exceptions you mention have wix-ready exceptions already (see the src\wix\exceptions directory).
-----Original Message----- From: Maillet, Ed [mailto:[email protected]] Sent: Friday, August 13, 2010 6:00 AM To: [email protected] Subject: [WiX-users] Gracefully handling Internal Extension Errors Hey all, For custom a Preprocessor or Compiler Extensions, what is the proper process/mechanism to gracefully handle internal errors. For example, if the GetVariableValue throws a NullReferenceException, or the Compiler extension ctor throws an exception, how should the exception be caught and reported so it shows up as something useful. Unhandled exceptions, when building inside Visual Studio, cause VS to do it's 'internal error would you like to report to Microsoft' flow. ----- Ed Unum Application Services In pleasant South Carolina ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
