Exceptions are a sometimes-frustrating part of debugging and developing. You can configure Visual Studio to deal differently with certain exceptions.

When debugging a program in Visual Studio, a number of situations may cause the debugger to enter break mode. When the debugger enters break mode, program execution is suspended, allowing you—the developer—the opportunity to examine and change the program variables. With Visual Studio 2005, you can even alter the program’s underlying source code when in break mode and have the program continue with the edited source.

A common way that break mode is entered is through breakpoints. Another way that break mode is regularly entered is when an exception is raised that is not handled by your application. Any exception that bubbles up out of your user code will cause the Visual Studio debugger to display information about the exception. While you will likely always want to be notified of an unhandled exception when debugging, you may want to break when an exception is thrown, regardless of whether or not it’s handled. Visual Studio can be easily customized to break immediately when a particular type of exception is thrown.

To customize Visual Studio’s behavior when encountering exceptions, go to Debug -> Exceptions or press Ctrl-Alt-E (Debug.Exceptions). This will display the Exceptions dialog.

Exception Dialog

The Exceptions dialog allows you to specify Visual Studio’s behavior when encountering an exception of a specific type. As discussed earlier, the default behavior is to continue when the exception is thrown and to break into the debugger if the exception is not handled. To modify these settings for a particular exception type, simply choose the exception type from the tree of exceptions and customize the radio buttons, indicating the debugger’s behavior.

Understand that changing the setting for a particular exception modifies the behavior for any of those derived exception types whose Use Parent Setting option is selected. By default, all derived exceptions have this Use Parent Setting checked, which means that, by default, changing the behavior of an exception will propagate those changes to its derived exceptions.

Source Error:

Line 1: <%@ Application Codebehind=”Global.asax.cs” Inherits=”Global’” %>

This error occurs when you create a new web application in asp.net using visual studio.net and without compiling the application, you try to browse a page in the application.

This occurs because of the Application DLL not having been formed.

asp.net will look in the Global Assembly Cache, and then in the application’s local bin directory. If it can’t find the class with the name you specified then it won’t load. When you do a codebehind file in Visual studio, you are writing a base class for your aspx file to inherit from – the HTML template you write in the aspx is inlined into the dynamically generated subclass’s Render method.

Even if you don’t put any code in your page, you still need to compile it as long as you put the Inherts Global in your Page directive.

To resolve this, Built the application using Ctrl + Shift + B or use F5 to build the application and then try to browse the application. The error will be resolved.