My talk on Visual studio 2015 debugging and profiling

1. Visual Studio 2015
Debugging and Profiling

2. About ME
Vidyasagar MSC
• Microsoft MVP – Games For Windows
• Developer at DELL
• Twitter : @IAmVMac
• http://about.me/mscvidyasagar

3. Developer’s
life Without
Debugger

4. Debugging : What’s new?
• Debugging UI refresh – Peak implemented
• Support for debugging lambda/LINQ expressions
DEMO

5. Limitations as of today
• Don’t currently support lambda expressions that require
calls to native function like LINQ-to-SQL
• ASP.NET 5 with 64-bit IIS and remote debugging ASP.NET
5 is not supported. The debugger will automatically use
the old expression evaluator in these cases.

6. Profiling
• Memory Usage Tool while debugging in Visual Studio 2015
• Not enabled by default
DEMO

7. (Not)Supported as of today
The Memory Usage tool in this Preview release only supports the following:
• Managed Desktop projects, including WPF, Windows Forms and Console
apps (you must disable the Visual Studio hosting process under the Debug
tab in the Project Properties)
• Managed Windows Store projects (not Windows Phone)
• Visual C++ projects, including Win32, MFC and Store apps
• ASP.NET projects
• ASP.NET vNext is not supported.
• The tool only shows memory from the server process. The iexplore process running
your HTML/JavaScript is not profiled.
• Only IIS Express, and not full IIS, is supported.

8. With VS 2015 CTP 6
• Exception Settings Tools Windows
• UI Debugging tools for XAML (WPF only)

9. With VS 2015 CTP 6
The Diagnostic Tools debugger window has the following
improvements:
• Supports 64-bit Windows Store apps
• The timeline zooms as necessary so the most recent break event is
always visible

10. Thanks
@IAmVMac
Learn more at
http://onestopdotnet.Wordpress.com