Enhancements to Debugging and Profiling in Visual Studio 2013 Update 2

Enhancements to Debugging and Profiling in Visual Studio 2013 Update 2

Rate This
  • Comments 5

Less than a year ago, I gave you a quick overview of the many investments we made to debugging and profiling in Visual Studio 2013 RTM and got some great feedback from you about what we’d done. Now, with Visual Studio 2013 Update 2 RC available for download, I wanted to run you through the enhancements we have made since last summer. We’ve done a lot, so this summary post mostly links to other posts.

I wanted to talk about two of the larger efforts we’ve made first: the Performance and Diagnostics hub (from where you can run tools such as the HTML UI Responsiveness tool, XAML UI Responsiveness tool, and Energy Consumption tool) and the ability to analyze .NET memory dumps.

 

With the Performance and Diagnostics hub, you now have the capability to run more than one tool at a time and look at the results in a combined view, so that you can cross-correlate activity from one tool with activity from another (e.g. "I can see that while my CPU was doing X, my UI was doing Y"). We’ve also introduced a new CPU Usage tool, for seeing where your .NET, C++, and JavaScript functions are using the CPU. And finally, we’ve added a Memory Usage tool for your .NET and C++ code to complement the JavaScript Memory tool we shipped previously.

 

 

Another large investment for VS2013 was the .NET memory dump tool, which includes the capability to inspect values of objects from the dump file. You can use this feature to investigate memory leaks with your Azure Web Site (new with Update 2 is the diffing capability for .diagsession files).  

There are several other notable features, two of which I’ll call out:

 

We’ve also invested to add support for the Windows Phone 8.1 platform, bringing feature parity to diagnosing issues with your XAML and JavaScript apps on the phone just as you can for Windows Store app development today. There are a lot of posts we’ve made on this topic:

 

Finally, for those of you trying the .NET Native Preview, you will want to also read about our brand new Debugging support for .NET Native apps.

 

As always, your feedback and questions on diagnostics are welcome in the MSDN Diagnostics forum.

Leave a Comment
  • Please add 5 and 5 and type the answer here:
  • Post
  • what is the level (x, pro, ult) for this on the desktop version?  Or what is the price point that this is available (on the desktop version)?

  • Hi "For the reading impaired". What do you mean by "this"? Also what do you mean by "desktop version"? The blog post lists many features, and each feature has a link to a more detailed blog post where you should be able to find the answer if the item is not available in the Express SKU.

  • Hi Daniel, I've just checked following detailed blog posts "Performance and Diagnostics Hub in Visual Studio 2013" and "XAML UI Responsiveness tool in Visual Studio 2013" and could not find the answer which SKU these tools belong to. It would be really very helpful if you could extend your post by this information.

    @YouGuysOutThere here you can check which edition of VS 2013 features belongs to: www.visualstudio.com/.../compare-visual-studio-products-vs.

  • Hi Elena, thanks for the pointers and the specific question. If the SKU is not listed then it is in VS Express for Windows (which is true for the Performance and Diagnostics hub and all the tools it currently exposes). The only current nuance is that the CPU Usage tool is in Express for Windows Store and Windows Phone apps, but for desktop apps it is in Pro+ (this is addressed in the comments on the corresponding blog post where you can leave your feedback on the tool).

  • What "blog post" do you mean?  I counted 21 links in fewer sentences in your write-up.  These things should come right out and say "requires ultimate", or "for the VS eXpress that does metro apps but not for the VS eXpress that does desktop apps".  This way us slumdawgs can skip it.

Page 1 of 1 (5 items)