Fix the exceptions that are raised and eaten internally after debugging unit tests
After debugging a unit test, several InvalidOperationException and CommunicationObjectAbortedException errors are thrown and caught within the unit test framework. If you go to Debug --> Exceptions and check Common Language Runtime Exceptions --> Thrown, then the debugger breaks on every one of these exceptions.
Can you please change the test framework code where it won't raise these exceptions? It's very annoying to have core Microsoft code that's throwing and eating exceptions after every unit test debugging session. I had hoped this would be fixed in VS 2012 Update 1, but it still has the same problem.
I originally logged this on Connect at http://connect.microsoft.com/VisualStudio/feedback/details/773660/debugging-unit-tests-raises-and-eats-several-exceptions-when-closing, and Microsoft suggested that I also post it here to get it scheduled sooner.
Bill Menees
shared this idea
2 comments
-
RobSiklos
commented
Doesn't turning off "Just my code" prevent these exceptions from breaking the debugger?
-
Ed Brey
commented
Besides the interruption of workflow, and the debugging loss that results from having to turn off break-on-throw for the offending exception types, the exceptions are obscure enough that it takes searching and finding requests like these to know that the problem isn't with my code.
