Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
With around 60 new features Visual Studio Update 3 has value through the entire development process from the new SDKs and emulators for Windows Phone and Windows Store development to the ~20 new features for Web developers including updates to ASP.NET Identity and Entity Framework. For team members focused on Application Lifecycle workflows there is a ton of new value for you too! If you are in a rush to get started you can skip directly to: Download Visual Studio 2013 Update 3 (also available on MSDN subscriber downloads).
For an end to end view of Visual Studio Update 3 please see:
For folks focusing on Application Lifecycle tools below is a list of top ALM Features in Visual Studio Update 3:
The Code Lens team has delivered performance optimizations, usability enhancements and a bunch of new features for Git users. For instance when you work with source control in Git and work items in TFS, you can view the CodeLens work items indicators for Git to obtain information about the work items associated with a method, property, or class.
The diagnostics team have been on fire in terms of shipping enhancements in this Visual Studio Update with 10 new experiences being shipped by this team alone. One of my favorite Application Insights demos is going directly from a performance event to an Intellitrace log and then to the line of code that caused that performance degradation….MAGIC!
The Team Foundation Server Team has been very busy – but much of their work was delivered through Visual Studio Online and new features like the ability to use Organization IDs and Integration into the new Azure portal. That said they have not forgotten about their on premises sweetheart and have added the ability to traverse the group hierarchy and you can now show or hide the In Progress items in the backlog.
Since the RC announcement Release Management has had the most features added. The ability to use PowerShell Desired State Configuration for deployments, be able to trigger Chef environments, agentless deployments and deploy to Azure and On-premises environments.
The Test Tools team continues to deliver test tools, functionality and value online. In the Test hub of Team Foundation Server Web Access you can now add custom fields and custom work flows for test plans and test suites, Manage Test Suites permission for granting access to test suites and track changes to test plans and test suites by using work item history. Cloud-based Load Tests can now deliver both standard and custom performance counters through integration with Application Insights. For more information on this and how to use Cloud Load Test to drive unit tests please see: Driving Unit Tests from Cloud Load Test
If you haven’t looked at Application Insights in a while you may be shocked to find out Application Insights now uses the Azure Preview portal to display monitoring data. Application Insights now is a 1st class citizen in the new Azure Portal:
https://portal.azure.com. In addition, the team has made searching your diagnostics logs even easier.
What application types are available with the CPU Usage Tool?
I have now tried with a native c++ console application and a .NET 4.5 console application and a .NET 4.5 Winforms application. Performance and Diagnostics shows "CPU Usage" as not applicable for selected target.
I have the exact same problem, I've had it since the RC. I'm amazed something like this slipped past the QA net. I'm actually tempted to go back to update 2. Maybe they can fix it.
The new app insites in the azure portal looks 'fancy' but it feels like feature wise it is 8 months behind what is in the old environment.
Any idea when you are going to 'light up' some more of the features? Installing update 3 replaced my existing extension so new apps all want to go to this new hardly started environment and app insights went from having some decent value to having almost none.
Thanks for your feedback regarding the Azure Preview Portal. While we are not yet at “par” with the Visual Studio Online (VSO) portal, we are working on lighting up new functionality every few sprints and would love to hear in more detail what functionality you are missing in the Azure Preview Portal that was in the Visual Studio Online Application Insights portal?
See this MSDN article msdn.microsoft.com/.../dn793604.aspx that has a section on how to move to the previous VSIX that will communicate with the VSO portal instead of the Preview portal.
@Rolf, Sean, the CPU Usage tool is not available on Windows 7. The CPU Usage tool will be available for all the project types you mentioned on Windows 8.1. If you are on Windows 8.1 and are not seeing the CPU Usage tool please use the feedback button in the top right-hand corner of Visual Studio to report a bug.