>>Or use the CallSTack and go back .. each line allows you to view the variables at that spot.
>
>Nope, CallsStack didn't work for me. The original line of code was not even in the Stack. In any case, it was because I tried using Convert.ToInt64 and the variable was empty.

As said - works with the call stack - don't forget to double click on the line in the stack. That will give you the same information as if you had put a breakpoint.

Found one exception so far : if an exception is thrown in a static initializer - you need to copy the stacktrace to the clipboard, paste it in notepad and look where it went wrong. Then you put a breakpoint on it