dotnetConf 11/14/2018 8:22 AM © 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Debugger Tips and Tricks dotnetConf 11/14/2018 8:22 AM Debugger Tips and Tricks Kaycee Anderson @Kayand2014 Nikhil Joglekar @Nikljogo © 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

“Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?” Brian Kernighan, Computer Scientist “As soon as we started programming, we found to our surprise that it wasn't as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs.” Sir Maurice Wilkes, Computer Scientist

Agenda Demos 20+ Tips and Tricks in Visual Studio 2015 dotnetConf 11/14/2018 8:22 AM Agenda Demos 20+ Tips and Tricks in Visual Studio 2015 2 New Things in Visual Studio “15” Preview Resources © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/14/2018 Demo © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Recap Debug Launch Targets Multiple Startup Projects IntelliTrace Exception Events Historical Debugging Debug.WriteLine Exception Settings Lambdas in the Immediate Window Set Next Statement Edit and Continue

Event List Enterprise: Look at events in the event list to understand timing of various operations in your app Community + Pro: see the history of break events and the values shown in PerfTips

PerfTips See elapsed time of code as you hit breakpoints and step F10

CPU Usage while Debugging Monitor the CPU graph for spikes Enable CPU Profiling and enter break mode to see what functions were consuming the most CPU cycles

Memory Usage Monitor the Memory graph to identify increase in memory consumption Take snapshots to get a breakdown of memory by type

Recap Tracepoints JSON Visualizer Debugger.IsAttached Debugger.Break Return Values Step into Specific Run to Cursor Pinned Data Tips Make Object Id Run To Cursor from Call Stack

Help us improve the debugger aka.ms/diagfb Subscriber Benefits: Opportunity to give feedback about future ideas Try out products and features before the general public

Resources Sample Code from our demos: https://github.com/Microsoft/vs-diag-samples Team blog: http://aka.ms/diagnosticsBlog Visual Studio Blog: http://blogs.msdn.com/visualstudio Debugging Performance Issues Using Visual Studio 2015 http://channel9.msdn.com/Events/Build/2015/3-731 Historical Debugging in Visual Studio 2015 with IntelliTrace https://channel9.msdn.com/Events/Build/2015/3-771