From the course: Visual Studio: Advanced Debugging Tools

A quick look at the Diagnostics window - Visual Studio Tutorial

From the course: Visual Studio: Advanced Debugging Tools

Start my 1-month free trial

A quick look at the Diagnostics window

- [Narrator] Let's start with a quick review of the Visual Studio diagnostics window. You've seen this window when debugging, it's on by default. I've learned over the years that developers often hide the diagnostics window and then forget that it's available. For this example, we're looking at this solution called Advanced debugging that contains three projects. The code is not important for this demo, it's merely a place to put a breakpoint. And that breakpoint will be in this debug WPF project. So I'll make that my startup project. Now we'll go look at the standalone. There's two buttons on this window. I'll activate the breakpoint by clicking in this top button. And the breakpoint itself is over here in the C-sharp file, online 15. We'll start a debug session by going to Start, then click on this top button, and now we've hit our breakpoint. This is the standard view of the C-sharp interactive debugger and the diagnostics window is not showing. And that's okay. There are many times when it's not necessary to have it visible when debugging. To bring it into view, go to the Debug menu and choose Show diagnostics tool. And this is the diagnostics tools' window. It's full of useful tools which we will explore in detail later in the course. Now I'll go ahead and click on continue and watch what's happening in the background. It's doing a live analysis of my application in this case you can see how much memory is being used by my application. So what a lot of developers will do is because this can be visually annoying, is to switch over to Visual Studio, and then close the diagnostics window. Let's see what happens the next time you debug the application. Now we'll start in the debugging session. The breakpoint and the diagnostics window does not appear until you re-enable it. So you'd have to go to debug windows show diagnostics tool. For the first part of this course we won't need to see this window. So let's close it for now.

Contents