Using ASPX – we catch general exceptions – well some messages are too general. Here is some advice emailed to me from a mentor and friend Sjoerd.
UPDATE: Be careful on what messages get thrown/exposed to the final client. If there are open data that is sensitive – the advice below might bee too revealing.
When catching errors, please make sure you bring back the following properties from the exception:
- Ex.StackTrace
- Ex.Message
- Ex.InnerException
He included these links
- http://www.dailycoding.com/Posts/are_you_throwing_exceptions_correctly.aspx
- http://stackoverflow.com/questions/4272579/how-to-print-full-stack-trace
If you like, you can throw an exception on purpose and look at what the properties will return you.