Which debugging feature of the Visual Studio IDE do you use the most. I agree that it depends on the scenario. But it turns out that people tend to use some features very often (eg Stacktrace) and some very rarely.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Which debugging feature of the Visual Studio IDE do you use the most. I agree that it depends on the scenario. But it turns out that people tend to use some features very often (eg Stacktrace) and some very rarely.
Apart from breakpoints and step in/out and run to cursor, I mainly use (auto)watches, stack trace, and the watch under mouse pointer. I think I use the latter the most.
For a “hidden” feature, I’d vote for debugger visualizers. Once I wrote an application that heavily manipulated bitmaps. I had some trouble, and wrote a visualizer to display the bitmaps in the memory and zoom on them. It was extremely useful (and easy to write).
Another useful thing is conditional breakpoints. I can’t recall the exact situation, but I remember I was happy to find out how versatile they are.
And, of course, edit-and-run without recompilation is very nice.