The cleanest way to handle all exceptions in C #

Question

I am learning the best way to handle all the exceptions of the application without much abuse of the code. The main goal here is to send exception information to an external platform such as Application Insights. So far, I have found the following methods:

• Castle Interceptor:
  This is the best approach so far, the fact is that in order for the methods to be intercepted, either the methods are virtual, or the class must be conjugated. Since I'm working on a really big application, these changes are undesirable.

• Developments:
  Using AppDomain UnhandledException should also be considered, but since I have several application domains that will need a lot of changes, they will randomly get confused with classes for exceptions only, which is not optimal since classes should not be mixed just because of exception handling. Besides the number of AppDomains, I also have several threads from which exceptions are not caught by such handlers.
  

• PostSharp:
  PostSharp works similarly to Castle, and the problem here, if I understood correctly, is that I will have to add attributes / decorators to all the methods that I want to intercept, as well as a not-so-good approach.

If anyone has suggestions for a better approach, I will be very grateful.

Answer 1

There is an excellent article located at https://dncmagazine.blob.core.windows.net/edition30/DNCMag-Issue30.pdf , which discusses error handling in large projects. Probably the least intrusive approach would be to use a global exception handler. I would also like to consider using a library such as log4net, because it can record exception information using multiple repositories (local file, SQL, etc.) and can be reconfigured from configuration files, which avoids code changes, recompilation and application distribution / installation.

For those new to DNCMag, this is a FREE magazine for coders with many great articles and can be viewed at http://www.dotnetcurry.com/magazine/