Handle All Your Plugin Exceptions In One Place, And Then Hide It!

In coding, one of the recommended best practices is to avoid creating duplicate code as it leads to maintenance issues. Therefore, it is advisable to let your Plugin Base class logic handle catching and logging exceptions. However, this creates problems when debugging unit tests because if the plugin throws an exception, the debugger will stop execution at the throw statement in the plugin base, and you won't see the actual line of code where the error occurred. Debugger attributes, such as the DebuggerStepThroughAttribute in the System.Diagnostics namespace, can be added to your base plugin class that contains the throw to force Visual Studio to stop debugging at the actual line where the exception occurred rather than at the plugin base exception handler logic. By doing so, you can save time and easily navigate the path to the exception. The base plugin call site is represented by the [External Code] line and can still be found in the actual exception stack trace. Follow this best practice when coding and enjoy happy coding!