Thanks for the fast reply. Answers inline...
1) Have you any other VS add-ons installed?
Just the TestDriven add-in, but this one shouldn't be affected by the
2) While debugging, do not run another VS, but CLR debugger instead.
And enable break on all exceptions just before you make the debugee VS crash
Also doesn't work - as soon as I type the method, I'm getting the "MS
Visual Studio has encountered a problem and needs to close" dialog
(usually) or VS just disappers suddenly (only once). When I try to start
debugging from this dialog, I've had different behaviours:
- an RS exception that was caught by the CLR debugger, but that one came
after the exception that caused VS to crash
- the opportunity to start a new VS 2005 for debugging. From there, I
landed in "alloc.c". It appears to be a Win32 exception when requiring a
block of memory from the heap.
Maybe it's my VS? - I'm lost here ;)