"Go" writing high-quality Code 157 recommendations for improving C # programs--Recommendation 65: Always handle uncaught exceptions

Recommendation 65: Always handle uncaught exceptions

Handling exceptions to catch is a basic feature for each application, and C # provides a UnhandledException event to receive notification of uncaught exceptions in the AppDomain. Common applications include the following:

 static  void  Main (string  [] args) {AppDomain.CurrentDomain.UnhandledExceptio n  + = new   Unhandledexceptioneventhandler (        Currentdomain_unhandledexception);  static  void  currentdomain_ UnhandledException (object   sender, UnhandledExceptionEventArgs e) {Exception error  = (Exception) E.exce            Ptionobject; Console.WriteLine (  " myhandler caught:   " + error.        Message); }

uncaught exceptions are usually run-time bugs, and we can currentdomain_unhandledexception in AppDomain.CurrentDomain.UnhandledException's registered event method. The uncaught exception information is logged in the log. The mechanism provided by UnhandledException does not prevent the application from terminating, which means that the application terminates after the Currentdomain_unhandledexception method is executed.

Use the ThreadException event in the WinForm program to handle UI thread exceptions and use the UnhandledException event to handle non-UI thread exceptions. ThreadException can prevent the application from terminating.

Turn from: 157 recommendations for writing high-quality code to improve C # programs Minjia

"Go" writing high-quality Code 157 recommendations for improving C # programs--Recommendation 65: Always handle uncaught exceptions