Diagnostic Sessions at Build 2015

Aaron Hallberg

If you’re attending Microsoft’s Build 2015 conference this week, make sure to come check out these three sessions focused entirely on diagnostic tools.

Debugger Tips and Tricks for .NET Developers with Visual Studio 2015

Session code: 3-677

Room: 2009

Time: Wednesday April 29, 5:00-6:00 PM

Every software developer has the need to debug problems in software, but we are rarely taught how to use the debugging tools available to us.  Come to this demo-driven session where we’ll learn how to make the most of the debugger to find bugs faster.  We’ll tour most of the debugger, throwing in tips and tricks as we go along, with a special focus on brand new enhancements in Visual Studio 2015.  Whatever your experience level we guarantee you’ll learn something new.

Debugging Performance Issues Using Visual Studio 2015

Session code: 3-731

Room: 2018

Time: Thursday April 30, 6:30-7:30 PM

Every application has performance requirements that must be satisfied.  In many cases the speed of the computer is good enough so you don’t have to think about it.  In many other cases you don’t notice problems until your customers report them. Come to this demo-driven session to learn how to use Visual Studio 2015 to continuously improve the performance of your applications during normal development.  You’ll learn how to use the new capability of running diagnostic tools with the debugger and how to use the tools without the debugger to both prevent and diagnose a broad range of performance issues.

Historical Debugging with IntelliTrace in Visual Studio 2015

Session code: 3-771

Room: 2009

Time: Friday May 1, 2:00-3:00 PM

Come to this all-demo session to learn how IntelliTrace in Visual Studio helps you minimize wasted time while debugging .NET applications. We’ll look at IntelliTrace’s ability to take the debugger back in time and examine the state of the application at interesting points in the past.  All in the context of the new Visual Studio 2015 IntelliTrace experience.


Discussion is closed.

Feedback usabilla icon