Another new feature that makes your coveted is a new-new application level event, you can find it in a part of a series of MyApplication. You can find a file called MyEvents.vb in the My Project project in the Solution Explorer. You can also click the View Code button on the Application panel and then view it in the code editor. These new application level events are similar to the application event in the Global.asax file in the ASP.NET application. A total of five events: · Shutdown · Startup · StartupNextInstance · NetworkavailabilityChanged · UnhandledException When the application started or off, the first three events were triggered. When the machine network status changes, the NetWorkavailabilityChanged event is triggered. In order to prevent the system from throwing an exception you have not handled in other places, you can also add code under the Unhandexception event. @ The following is the text for your reference @Application Level EventsAnother new feature you'll want to take advantage of is a new set of Application-level events available in a partial class named MyApplication. Look for a file named MyEvents.vb under the My Project item in Solution Explorer. You can also find this file behind the View Code button on the Application tab in the application designer. These new Application-level events are similar to the application events in the global.asax file in an ASP.NET application. Five events are exposed: • Shutdown • Startup • StartupNextInstance • NetworkAvailabilityChanged • UnhandledExceptionThe first three events are fired as the application starts up and shuts down NetworkAvailabilityChanged fires when the network state changes on the machine Put code in the UnhandledException event in case an exception.. Is Thrown That You don't handle anywhere else.
