Showing results for 2013 - Page 4 of 15 - Azure DevOps Blog

In Visual Studio 2012, we introduced a new managed debug engine that provides us the ability to more rapidly add new features compared to the older implementation. This can be seen by the number of features introduced in Visual Studio 2013 after only a single year including Managed Return Values, .NET 64-bit Edit and Continue, Async Callstacks Enha...

IntelliTrace is not supported in Silverlight due to the security model. IntelliTrace is supported for Windows Communication Foundation (WCF) projects hosted in a web server such as Internet Information Server (IIS) or Internet Information Server Express (IIS Express). When debugging an application in Visual Studio Ultimate that contains both Silver...

The Microsoft Monitoring Agent does a great job of logging unexpected exceptions that occur within your application. NullReferenceExceptions are one of the most frequent types of exceptions that are encountered. The default settings for the Microsoft Monitoring Agent are configured to optimize data collection and does not record null parameter valu...

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 data breakpoints using earlier versions of Visual Studio please see the MSDN Documentation. Data breakpoints are a powerful feature that is curren...

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 conditional breakpoints using earlier versions of Visual Studio please see the MSDN documentation. In earlier posts, we showed hit count breakpoin...

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 conditional breakpoints using earlier versions of Visual Studio please see the MSDN documentation.  The code used in the examples below is availabl...

This blog post is part of a series on breakpoints in the Visual Studio debugger and has been updated to reflect the experience in Visual Studio 2015.  In this post, we will show the function breakpoints feature of Visual Studio and how this feature can be used to save you time while debugging. Dealing with Overloads Let’s say that you want the de...

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...