<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to handle Unhandled Exceptions</title><link>http://blogs.msdn.com/tom_krueger/archive/2005/02/17/375602.aspx</link><description>When an exception occurs is thrown in your application, but is never caught the application ends up crashing. Not exactly a user friendly application. So that you can better handle these unhandled exceptions and at the minimum close the application gracefully</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: How to handle Unhandled Exceptions</title><link>http://blogs.msdn.com/tom_krueger/archive/2005/02/17/375602.aspx#375614</link><pubDate>Thu, 17 Feb 2005 21:49:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:375614</guid><dc:creator>Nuz</dc:creator><description>My question is if I use this in my asp.net application, I should NOT use the static type in the unhandled exception handler. Correct? Great Tip btw!!!</description></item><item><title>re: How to handle Unhandled Exceptions</title><link>http://blogs.msdn.com/tom_krueger/archive/2005/02/17/375602.aspx#375646</link><pubDate>Thu, 17 Feb 2005 22:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:375646</guid><dc:creator>Tom Krueger</dc:creator><description>Hello,  &lt;br&gt;&lt;br&gt;Yes that would be correct that you would not want to make this type of functionality static in a web application.  However, in a web app, unhandled exceptions are handled differently.  Main does not exist in a web application, however, in the Web.config you can specify a page to display when an exception is not handled. &lt;br&gt;&lt;br&gt;Take care,&lt;br&gt;&lt;br&gt;Tom</description></item><item><title>re: How to handle Unhandled Exceptions</title><link>http://blogs.msdn.com/tom_krueger/archive/2005/02/17/375602.aspx#375655</link><pubDate>Thu, 17 Feb 2005 22:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:375655</guid><dc:creator>Tom Krueger</dc:creator><description>Kind of funny,&lt;br&gt;&lt;br&gt;In my last response, I couldn't remember the config tag for specifying the error page so I didn't put it knowing if you look at the web config you would find it.  Then when I clicked submit to post my response, the site gave me an error screen displaying the webconfig.  So I copied the tag and here it is.&lt;br&gt;&lt;br&gt;&amp;lt;customErrors mode=&amp;quot;RemoteOnly&amp;quot; defaultRedirect=&amp;quot;mycustompage.htm&amp;quot;/&amp;gt;&lt;br&gt;&lt;br&gt;Tom</description></item><item><title>re: How to handle Unhandled Exceptions</title><link>http://blogs.msdn.com/tom_krueger/archive/2005/02/17/375602.aspx#375971</link><pubDate>Fri, 18 Feb 2005 09:30:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:375971</guid><dc:creator>Daniel Moth</dc:creator><description>I have the full story on unhandled exceptions for both .NET 1.0 and .NET 2.0 (for both CF and full fx) on my blog. A good starting point is this one:&lt;br&gt;&lt;a target="_new" href="http://www.danielmoth.com/Blog/2004/12/appdomainunhandledexception-part-1.html"&gt;http://www.danielmoth.com/Blog/2004/12/appdomainunhandledexception-part-1.html&lt;/a&gt;</description></item><item><title>Global Exception Handling in C#</title><link>http://blogs.msdn.com/tom_krueger/archive/2005/02/17/375602.aspx#8366366</link><pubDate>Mon, 07 Apr 2008 23:21:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8366366</guid><dc:creator>Random Binary</dc:creator><description>&lt;p&gt;Global Exception Handling in C#&lt;/p&gt;
</description></item></channel></rss>