Analytics gives us the ability to understand our users and what they are experiencing, so we can build the right applications for them. It alerts us quickly to any issues and helps us diagnose them rapidly so as to provide users with the best possible service level.
UPDATED: Jun 12, 2015
Well, we’ve almost made it through everything I originally put into this post. The Kanban metrics are the one things we’re still waiting on.
Swim lanes landed on VSO last week: https://www.visualstudio.com/news/2015-jun-3-vso
Last month we rolled out our new backlog navigation,
Our latest improvements to Application Insights Diagnostic Search include a personal favorite of mine, Property filters. While it’s easy to setup logging from your application, we don’t want you and your team to spend a lot time trying to search your logs.
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.
Note: this post has been updated for Visual Studio 2015 RTM
This blog post introduces the new Diagnostic Tools window in Visual Studio 2015. First we’ll define what we mean by diagnostic tools, then we’ll introduce the Diagnostic Tools window, and then we’ll dive into the different tools in the window.
Debugging is part of every developer’s routine. Something that is not often talked about is how much time can be wasted trying to find the root cause of a bug. A debugging session typically starts with your best guess of where to put the first breakpoint.
Performance and load testing is a very important part of the Application Lifecycle. You’d want to do this at least every time prior to deploying the latest changes to production. To determine how well your software responds to various levels of usage,
We are happy to let you know that over the last couple of weeks we have added a set of new features to our simplified browser-based experience for Cloud Load Testing.
In addition to the capabilities mentioned in the blog here –
This post has been updated to reflect the experience while using Visual Studio 2015.
If you have spent any time coding, odds are that you have had to deal with Exception Handling. In Visual Studio, when exceptions are thrown or end up unhandled,
Application Insights can collect telemetry from your application at any stage in its development, from debugging to live production. By default, all these different streams will go into the same bucket and interfere with each other. For example, if you run heavy stress tests,