1 "Run To" button just at the head of the lines 2 Pin the "Watch" window (it can't be in another monitor, BTW) 3 DebuggerDisplay to show customized information in the Watch/Auto/Local window 4 Text Visualizer(XML, HTML, JSON) 5 Actions in Breakpoint setting, log a message to the Output window, also in the "Diagnostic Tools -> Events" window
This was really good. Only knew 3 of these tips, and the tracing breakpoints are going to be so helpful. One note about conditional breakpoints, they slow down execution a lot, even compared to debug speed, so use them sparingly.
Great video. Love the debuggerdisplay feature. As an olidie I remember conditional break points in VS2005. Nothing to do with programming but good to see "Pere Goriot" in the book list.
Very helpful video :) Just one thing: many videos on Channel 9 and other Microsoft's channels are described with timeline. something like: 2:45 : Run Execution to line 3:30 : Pin Watching item..... It's a lot easier for me to review video like that, instead of viewing full video with many things i have already known.
I couldn't agree more. Also, it would be great if you can add bookmarks in the video so people can jump to the main points just like in other sites like Ud*my. JustMy2Cents.
I have been using Visual Studio since day one. I didn't know about the debuggerdisplay attribute on the class object. To display the objects of a list or arrray in a data tip, I have always override the ToString() function and write all the logic in there. I have never seen the run to click feature, seems handy.
You don't need to restart the application if you add/change a conditional breakpoint. Maybe your app needs to be restarted to reach the code you are debugging, but then that's simply because how your app is written.
She didn't restart because of the breakpoint. She restarted because of state the app was in. In this example she could've just dragged the current step to the beginning. Which she know because she shows it in another video.
11:30 breakpoint Actions 14:00 Output Windows Why did my Visual Studio 2019 Community print it in the Immediate Window, not in Output? Thanks. 感恩感恩 南無阿彌陀佛
Go upvote "Support data breakpoints for .NET framework" here!: developercommunity.visualstudio.com/idea/518713/support-data-breakpoints-for-net-framework.html
Why the black screen? with faint dark green or faint dark blue text? with no contrast? To read the screen have to use magnifier at 200x. Are we fancy and important if we use the black screen? Oh Im so sophisticated because I saw that one guy use the dark background so I want to look smart? You cannot prefer this over the normal background?? I came from the monochrome crt world. Those screens had contrast, this does not, its not readable.
