With the latest Team Foundation Service update and with Visual Studio Team Foundation Server 2013 RTM, we have changed the names of all process templates. From now on, the process template names will reflect the version of Team Foundation Server that supports their download.
Previously we told you about the initial integration between System Center Operations Manager and Visual Studio IntelliTrace that supports exporting exception data from System Center to Visual Studio using IntelliTrace. We are pleased to announce with the release of System Center 2012 R2 and Visual Studio Ultimate 2013 that performance data can now be exported to IntelliTrace format as well.
In TFS 2010 we released the reports to show the overview of the backlog and the progress of the these items. It depends on your process template which reports were installed for you:
As Charles announced earlier today, we’ve just released Visual Studio and Team Foundation Server 2013. I’m here today to briefly highlight what’s new in version control and TFBuild and to advise you about a known issue in TFBuild that we’re working to fix.
Visual Studio 2013 has been released to the web!
– Download Visual Studio 2013
– Save the date for Visual Studio 2013 Launch on Nov 13th
– Read the release announcements on Soma’s blog (for VS 2013 RTM) and Blogging Windows (for Windows 8.1)
This release has been an amazing ride.
Hello, I am Andrew Chan, a Program Manager on the Visual Studio Debugger Team and in this post I would like to go over an improvement we’ve made to opening dumps of 32-bit processes in Visual Studio. In a nutshell, Visual Studio is now able to open dumps of 32-bit processes that are collected using Task Manager on 64-bit versions of Windows!
In this blog post, we will cover the changes we have made in the way we load symbols in the remote debugging experience for .NET languages. This applies to remote debugging for .NET languages and other languages will load symbols locally.
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,
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 Silverlight and WCF services projects you may encounter an IntelliTrace message indicating that IntelliTrace data is not being collected.
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 values.