Thursday, 22 April 2010

What to do with ASP.NET exceptions and specifically handling ELMAH!

Ever wonder which is the best way to report your elmah based asp.net exceptions?

Should you send the error to an email address - what if the recipient is on holiday?

Should we send the exception emails to a centralized account - theres a lot of duplication there, and which recipient will deal with the email?

How about posting the exceptions to twitter - this is a bit too public for my liking do we really want connection strings etc being posted here?

How about this, a layer built on top of ELMAH to handle all of these requirements and automatically handle exceptions and presentation of these to the user in a beautiful way:

http://aspexceptionreporter.codeplex.com/

Your thoughts......

1 comment:

Anonymous said...

If I were to weigh in, I would crosspost them to Twitter, Facebook and MySpace - that would be an ideal "balance".