WPF Exception - Send Error Report
-
I have an Exception Window dialog that I pop up when an error occurs. On it is a "Send Error Report" button that opens an email. I wrote out the Exception.ToString() to a file and attached it to the email. I feel like this isn't enough info to accurately debug. So the question is, what else would you send?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I have an Exception Window dialog that I pop up when an error occurs. On it is a "Send Error Report" button that opens an email. I wrote out the Exception.ToString() to a file and attached it to the email. I feel like this isn't enough info to accurately debug. So the question is, what else would you send?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Kevin Marois wrote:
what else would you send?
Stack trace, source code around the place that caused the exception, assuming you can capture such information. Really it is up to you to decide what information you would need in order to diagnose what went wrong.
-
I have an Exception Window dialog that I pop up when an error occurs. On it is a "Send Error Report" button that opens an email. I wrote out the Exception.ToString() to a file and attached it to the email. I feel like this isn't enough info to accurately debug. So the question is, what else would you send?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I have an Exception Window dialog that I pop up when an error occurs. On it is a "Send Error Report" button that opens an email. I wrote out the Exception.ToString() to a file and attached it to the email. I feel like this isn't enough info to accurately debug. So the question is, what else would you send?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
If the issue involved a "class", as in say a WCF message API, I would serialize the class to XML and include that also in the report (besides the stack trace, recursive inner exceptions, etc.) Also: user id, machine name, OS, date and time, app version / file dates.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
I have an Exception Window dialog that I pop up when an error occurs. On it is a "Send Error Report" button that opens an email. I wrote out the Exception.ToString() to a file and attached it to the email. I feel like this isn't enough info to accurately debug. So the question is, what else would you send?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I send the stack trace and the method name as well as the error message.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP