AspNet4YouTop 10sDevelopers WorldForums
Home
About
ASPNet Books
ASPNet Sites
ASPNet Hosters
View Articles
Search Articles
Authors
View Forums
 
Quick Menus
HOME
About
AspNet4You Forums
Articles
Authors
Search
Articles Summary
Articles(RSSFeed)
AspNet Books
AspNet Sites
AspNet Hosters
 Top 10 ASP.NET Books 
Professional ASP.NET 1.1
Essential ASP.NET With Examples in C#
ASP.NET Unleashed
Programming Data Driven Web Applications with ASP.NET
Professional ASP.NET Web Services
Beginning ASP.NET 1.1 with Visual C# .NET 2003
Programming Microsoft ASP.NET
Beginning ASP.NET Databases Using VB.NET
ASP.NET Security
Developing Microsoft ASP.NET Server Controls and Components
More...
 Top 10 ASP.NET Hosters 
WebHost4Life
DiscountASP.NET
MaximumASP
Brinkster
ORCS Web
myhosting.com
ISQSolutions
ASPwebhosting.com, LLC
Active ISP
Aquest Hosting
More...
 Top 10 ASP.NET Sites 
Asp.Net
GotDotNet
4GuysFromRolla.com
123aspx.com
EggHeadCafe.com
CShrp.Net
.NET 247
DevelopersDex.com
Csharp-Corner.com
dotnetspider
More...
Search Articles
Google
ASPNET4YOU      
Category:   Search Type:   Match Type:  
ASP.NET 2.0 Unhandled Exception Issues
Author: Bromberg, PeterPosted: 3/14/2006 6:24:13 AM
In a previous article detailing some techniques for dealing with Unhandled Exceptions, I made mention of the fact that in the .NET 2.0 Framework, unlike in .NET 1.1, an unhandled exception will smartly bring the AppDomain to a screeching halt, often without providing so much as a clue about exactly what went wrong and where in your code it happened. I also provided some sample code that can help in this area. However, I didn't go very deeply into the situation where this may happen in an ASP.NET 2.0 application other than to provide some sample code for handling the Application_Error event in global.asax. In this article, I'll continue with more details on dealing with this issue in ASP.NET 2.0.
Read this article from external site
Terms and Conditions