Question

I have some framework / AOP code that logs exceptions from methods called deeper inside…

try {
  ..invoke inner code...
}
catch (Exception e) {
  log(e);
  throw;
}

This works great except for one thing…when my team tries to debug their code in Studio, they only see the exception happening in the logging code (since it gets handled, and then thrown from there).

Is there any way I can get Studio to ignore that my code is catching/throwing an exception…or to inspect the exception on it’s way through without catching it?

UPDATE:
The issue is that I have framework code that prevents the correct break-point for the real exception from being hit. I am aware that the debugger in visual studio is capable of fine-grained configuration, and I am hoping that someone here can provide a higher level insight than “Learn VS2010 in 31 Hours” does. I simply want to BOTH log the exceptions that are caused in inner code, AND have the break happen at the site of the error WITHOUT turning on ‘Break on All Exceptions’ which would cause my team to spend 5 minutes pressing the ‘Continue’ button every time they launched the app (but that’s another story).

UPDATE 2:
The primary question here, is how can I log the exception, but have the debugger not stop on the ‘throw’ in my logger, but on the initial exception, without having the debugger stop on all exceptions thrown.

Answer 1

I’ve done some digging, and the answer in 1349613 put me on a good scent. I’ve added the attribute:

[DebuggerNonUserCode]

To my logging class. Now when the internal, invoked code throws an exception, the debugger ignores the logging code, and it’s Try/Catch block, and goes straight to the internal exception.