On April 12th, Azure announced the General Availability of Azure AD B2B Collaboration. In a nutshell, it allows you to easily invite guests into your Azure Active Directory (AAD). As a Visual Studio Team Services customer, this enables you to invite guests into your AAD backed VSTS accounts in two steps:
Step 1: In the Azure portal,
With Visual Studio 2015 RTM we shipped the first version of the Diagnostic Tools window. In Visual Studio 2015 Update 1 we’ve made the following improvements to the Events tab of the Diagnostic Tools window to help you read through and understand the list of events even faster and more efficiently than before:
Improved the filtering menu
Added the ability to search
Added category prefixes to all events
In this blog post I’m going to talk about IntelliTrace’s default configuration and the ability to opt-in to capture method call information. If you haven’t done so already, check out the announcement of IntelliTrace in Visual Studio 2015 which gives you an overview of IntelliTrace and its improved UI.
In this blog post I am going to walk you through using IntelliTrace in Visual Studio 2015 to deal with two exception-related scenarios:
Finding swallowed exceptions and fixing the bad exception handling
Finding the source of exceptions in async code
If you haven’t done so already,
In this blog post I am going to walk you through how to collect data from a windows service using the IntelliTrace Standalone Collector. For the purpose of this post I will be using a windows service I created called “MyWindowsService”.
If you haven’t done so already, check out the announcement of IntelliTrace in Visual Studio Enterprise 2015 which gives you an overview of IntelliTrace and its UI. Since the release of Visual Studio Enterprise 2015 RC, IntelliTrace supports the ability to attach to running processes.
In this blog post I am going to walk you through fixing a bug using IntelliTrace in Visual Studio 2015. If you haven’t done so already, check out the announcement of IntelliTrace in Visual Studio 2015 which gives you an overview of IntelliTrace and its UI.
As you probably already know, Visual Studio offers an enhanced debugging experience through the use of IntelliTrace. Your application’s execution is recorded by IntelliTrace and you can navigate through time, both backwards and forwards, and examine your code as you normally would during a debugging session by interacting with the Call Stack and Locals windows.
The Output window is a veteran in the war against bugs and has been part of Visual Studio since its very first release. It is comprised of a collection of text panes that communicate information to the user:
The Output window can be extended by adding to its collection of text panes programmatically,
In this blog post I am going to walk you through fixing a bug using IntelliTrace in Visual Studio 2015. If you haven’t done so already, check out the announcement of IntelliTrace in Visual Studio 2015 which gives you an overview of IntelliTrace and its UI.
