This blog post is part of a series on breakpoints in the Visual Studio debugger and has been updated to reflect the experience of using Visual Studio 2015. If you are interested in details about setting hit count breakpoints using earlier versions of Visual Studio please see the MSDN documentation. As mentioned in an earlier post, we will be writi...
You are likely familiar with the basic breakpoints functionality in Visual Studio. You click in the editor gutter/margin to create a red circle next to a line of code, and then your app stops at that location when any thread in your code reaches that location, so that you can inspect state using the debugger windows. What you may not...
This post is about a small featurette we added to one of the debugger windows – not a huge item, but sometimes for some people it is the little things that please them and so we decided that it was worth blogging about this feature. When you are debugging a large application, using the Modules window can be difficult because there are a...
As was introduced in the Microsoft Monitoring Agent blog post, the Microsoft Monitoring Agent provides a new capability to monitor IIS hosted applications and record performance violations in your application. Refer to the previous post and this MSDN article for details on using the Microsoft Monitoring Agent for monitoring your application and cre...
We are very pleased to announce the RTM version of the brand new Microsoft Monitoring Agent. This new tool incorporates the capabilities introduced with Visual Studio 2012’s IntelliTrace Standalone Collector and adds a ton of new features and capabilities. You can now download the Microsoft Monitoring Agent and install on any server in your ...
If you’ve ever debugged a JavaScript Windows Store app there’s a very good chance that you accidentally ended up in either “Function code [dynamic]” or “base.js” without knowing how you got there and with no clear way to get back out. To help address this, we’ve introduced a feature called “Just My Code” (JMC) for JavaScript in Windows Store apps w...
Update: this blog post has been updated for Visual Studio 2013 Update 3 – enjoy! If you attended our Build conference or watched some of the videos, you may have seen some of the new profiling tools and our Performance and Diagnostics hub. This blog post will provide an overview of the hub and the various performance analysis tools that we have bu...
(Posting for a team mate and friend Pratap Lakshman) From the perspective of interaction-performance applications need to be “fast” and “fluid” - fast to launch, to navigate between pages, to react to changes in orientation, and fluid in scrolling, in panning and in animations. This post introduces the XAML UI Responsiveness tool, a new tool in...
(Posting for a team mate: Shiv Prashant Sood) Battery draining applications result in bad customer experience and poor ratings. Optimal battery usage is an important aspect that a developer must consider. This post introduces the Energy Consumption tool, a new tool in the Visual Studio Performance and Diagnostics hub that enables you to optimize y...
This post (addressing uservoice feedback on CA) was written by Nat Ayewah, a member of the code analysis team in Windows Last year's release of Visual Studio 2012 marked a significant update to the Code Analysis experience in Visual Studio. We made code analysis available in more editions of Visual Studio, introduced a new user interface for v...
