Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.
How you choose to manage unhandled exceptions in your ASP.NET application makes a big difference to your users, as well as the site's administrators and developers. Presenting the right information, in the right way, to the right people is part of designing a fulfilling overall user experience.
As you'll recall, earlier I presented a brief discussion about exception propagation. You learned how thrown exceptions are passed up the call stack, and that once an exception reaches the original calling method without being caught, execution stops and the ASP.NET runtime takes over. Let's now take a look at what happens from there.