Visual Studio Debugger
Speaking of tracing every line of code, a lesson that I have had to learn and relearn a couple of times over the years is that sometimes when you are really stuck, the best thing you can do is set a breakpoint, a point in the code that tells the debugger to stop execution, set up to watch a specific variable, and start stepping in and out of methods.
It was not that long ago that I had spent 6 hours with no luck trying to figure out an issue. I set up the Visual Studio Debugger and watched the call stack for a single pass through and noted an odd occurrence--it was fixed in 3 minutes. Seriously, 3 minutes after hours of beating my head against a wall--I can be stubborn at times. Let's have a look at the currentBallSpeed ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access