Geeks With Blogs

WinToolZone - Spelunking Microsoft Technologies
I work as a developer on the Common Language Runtime (CLR) team, specifically in the areas of exception handling and CLR hosting.

The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Inside and Out... An attempt to understand technology better...

One always strives to write exception safe application but there are times when an exception can go unhandled.

In the .NET Framework, the AppDomain class exposes the UnhandledException event that can be used by by the managed application to know when an exception has gone unhandled. In the writeup, AppDomains and Unhandled Exception Notifications, I discuss the specifics of when and how this notification is made, what is the relationship between the thread that had unhandled exception and the AppDomain(s) for which this notification will be done and what should be done during the notification callback.

The source code for the article can be downloaded from here.

Posted on Saturday, December 15, 2007 9:46 PM .NET Framework , Articles , Development , CLR | Back to top

Comments on this post: [Article] AppDomains and Unhandled Exception Notifications

# re: [Article] AppDomains and Unhandled Exception Notifications
Requesting Gravatar...
this is good
Left by naishadh on Dec 24, 2007 3:25 AM

Your comment:
 (will show your gravatar)

Copyright © Gaurav Khanna | Powered by: