Don't catch all exceptions

posted by  hjwin (10)  16 months ago (blogs.msdn.com)

One of the best practices on exception is don't catch all exceptions. There are many reasons why this is a best practice. For example, You want to look at the application state when the exception is thrown so that you can understand exactly why the exception is thrown. The exact state is often lost when exception is caught and application is continued.

Here is another example why should not catch all the exceptions.

One team found a strange deadlock when turning on fusion binding log. After a long try and diagnose, we finally understand what is going on.

By default f