Code doesn't always go as planned. It would be great if we all could write code that works perfectly all the time but ultimately bugs will creep in and our code never works right the first time.

I admit it: I don't use the Watch window much. When I hit a breakpoint and want to know what the current value is in a variable that's near the breakpoint, I'll either type "?variableName" in the ...

Due to the size and complexity of the code, however, tracking this down by stepping through the code in the debugger (or by manually tracing through the code) is very time consuming.<br><br>So, ...

Debugging mouse events is especially confusing, because when the debugger stops the code, most of the events go away! What tactics can we use in these situations? When you work on an editor-style ...

March 2021 update to Microsoft’s open source code editor features an inline menu for editing conditions and hit counts for function breakpoints, giving users more control. Microsoft’s Visual Studio ...

As is the custom, the code which works perfectly in your local environment rarely works as perfectly in your remote test environment. Some issues can only be reproduced on the different hardware ...