Occurs when the application encounters an unhandled exception.
Assembly: Microsoft.VisualBasic (in Microsoft.VisualBasic.dll)
An application raises the UnhandledException event when it encounters an unhandled exception. This event is part of the Visual Basic Application model. For more information, see Overview of the Visual Basic Application Model.
You can use the Exception property of the e parameter to access the unhandled exception that caused this event.
You can use the ExitApplication property of the e parameter to control whether the application exits. By default, ExitApplication is True. Therefore, the application exits after completing the UnhandledException event handler. You can set the value to False in the UnhandledException event handler to keep the application running, and have it return to a waiting state.
The code for the UnhandledException event handler is stored in the ApplicationEvents.vb file, which is hidden by default.
To access the Code Editor window for application events
For more information, see Application Page, Project Designer (Visual Basic).
The Visual Basic compiler prevents applications that are built for debugging from raising this event, to enable a debugger to handle the unhandled exceptions. This means that if you are testing your application by running it under the Visual Studio Integrated Development Environment debugger, your UnhandledException event handler will not be called. For more information about building applications for debugging, see /debug (Visual Basic).
The following table lists examples of tasks that involve the My.Application.UnhandledException event.
Log unhandled exceptions
Availability by Project Type
Windows Forms Application
Windows Forms Control Library
Web Control Library
This example uses the My.Application.UnhandledException event to log any unhandled exceptions.
You must enter the code in the Code Editor window for application events. To access this window, follow the procedure found in this topic's Remarks section. For more information, see Application Page, Project Designer (Visual Basic).
Because the UnhandledException event is not raised when a debugger is attached to the application, you have to run this example outside the Visual Studio Integrated Development Environment.
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.