so why not use the latest version? Even if you still compile using VS 2013, you can open projects in VS2015, change the Platform Toolset to the version you need, and that way you're using the better debugger. Visual Studio 2015 offers a number of features for debugging.Manage breakpoints: Do you know how to set breakpoints, or how to enable or disable breakpoints? Did you know you can even export breakpoints?.

Learn the keyboard shortcuts! You should at least know the essential tasks like running the debugger, stepping in/out/over, continuing execution.

Things you should do to get familiar with the IDE: This time out, let's start fresh and look at the basics of the VS IDE.

We'll also look at how to get more information about objects while debugging, how to investigate lots of objects, mouse events, and debugging visualizers.

How to control to which function the debugger can step intoĪnd that's just for starters.

How to improve the logger so that you can quickly move to the message source.

How to change the version of the code at runtime (that way, you can test two or more solutions without recompiling).

That's the aim here, and so I'd like to share a few tips and encourage you to search for even more advanced ways to use the debugger. For me, it's crucial to know how to use that tool efficiently. With the Visual Studio IDE you get one of the best-integrated debuggers for C++. The reality is that sooner or later you will encounter a situation where the debugger will save your code and/or career! Some might argue that it's best not to touch the debugger at all (and just write clean C++ code). We all know that debugging is an important part of software development process.

Visual studio code c++ debugger