Friday, June 08, 2007 11:30 AM
I just wanted to throw this out there in case anyone else runs across this. If you are using
TestDriven.Net with Visual Studio 2005 first chance exceptions may not work as expected. If you have your debugger set to break on first chance exceptions and are debugging a unit test with TestDriven.NET 2.0 any first chance exception may actually cause your debugging session to end rather than to break as you would expect.
The solution to this is to set the project in which you're currently debugging as your startup project. I've been seeing this for the past few days but this is a relatively new machine so I can't be sure if this has always been the case or if this is a recent phenomenon specific to this machine and install. Regardless, this seemed to fix the issue for me.
By the way, I also noticed the same behavior in
R#'s Unit Test Runner (v2.5.2).
In case you're not familiar with first chance exceptions you can find out more about them
here.