New Debugging Features in Visual Studio 2015

Debugging, diagnostics and profiling are fundamental stages in software development that ensures that all errors, bugs and performance bottlenecks are found and resolved, before the application is deployed.
Although some 3rd party profiling and debugging tools like RedGate’s Ants Performance Profiler for .NET applications makes the job easy for you Visual Studio 2015 and recent Visual Studio 2013 updates have also introduced new capabilities to maximize developer productivity and improve code quality.

Some new debugging features in Visual Studio 2015 RC are as follows:
• Understanding Debugging with Stepping
• Debugging a specific method out of multiple method calls from a single statement 
• Debugging Code Data Visualizer 
• Managing the Display of the Debugged Data 
• Evaluating lambda expressions in debugger watch window

New Debugging Features in Visual Studio 2015 RC

Managed Edit and Continue on Attach

As of RC, you can edit and continue when you attach to .NET applications and when the environment variable complus_forceencis set to 1 in the target process.

Breakpoint Configuration

The new Breakpoint Settings window allows you to specify conditions and actions for your breakpoints. The window includes improved IntelliSense support for breakpoint conditions and actions. You can use undo (CTRL+Z) to restore deleted breakpoints.

Lambda Expressions in Debugger Windows

You can now use lambda expressions in the Watch, Immediate, and other debugger windows in C# and Visual Basic.

PerfTips

You can use the PerfTips feature to see how long code took to execute directly in the editor when you set breakpoints and step with the debugger.

GPU Usage

The GPU Usage tool can be used to understand GPU usage of DirectX applications. Frame Time, Frame Rate, and GPU Utilization graphs are available while the applications are running live. In addition, by collecting and analyzing detailed GPU usage data, this tool can provide insights into the CPU and GPU execution time of each individual DirectX event, and therefore can be useful to determine whether the CPU or GPU is the performance bottleneck.