The call stack is the tool for this sort of stuff. You can look down the stack for what/where in your code the exception was triggered. You should keep the stack window available always while debugging.
It is handy to see what is going on when you set breakpoints also. The source is available for the code on the stack most of the time. Then you can hover to see values of stuff that is not yours but you are using.
Let the symbols server load everything up. It is cheap while debugging and eliminates a lot of guess work.
The call stack is the tool for this sort of stuff. You can look down the stack for what/where in your code the exception was triggered. You should keep the stack window available always while debugging.
It is handy to see what is going on when you set breakpoints also. The source is available for the code on the stack most of the time. Then you can hover to see values of stuff that is not yours but you are using.
Let the symbols server load everything up. It is cheap while debugging and eliminates a lot of guess work.