News

Visual Studio 2013 Update 3 Gets its First CTP

The Update comes fewer than two weeks after the official release of Update 2 at TechEd North America.

It's been about a year since Microsoft kicked off its new vision of quicker, smaller updates to Visual Studio, instead of a few massive updates every so often. As stated at the time by S. "Soma" Somasegar, corporate vice president of Microsoft's Developer Division:

"We wanted to get away from this old model where we deliver a version of Visual Studio today, and then you have to wait two years, three years, four years -- who knows how long you'd have to wait before we'd get you the next version.”

He wasn't joking. Fewer than two weeks since the release of Visual Studio 2013 Update 2, along comes the first public version of Visual Studio 2013 Update 3 -- Community Technology Preview (CTP) 1.  

Update 3 appears to be a fairly minor upgrade, with no significant new features. That doesn't mean it has nothing of interest for developers, however. Improvements have been made in a number of areas, including:

  • IntelliTrace, which is now more tightly integrated with Application Insights.
  • Profiler, with an expanded Performance and Diagnostics hub.
  • Testing tools, which now allows custom fields and custom work flows for test plans and test suites.
  • The Visual Studio IDE, with numerous enhancements to CodeLens, Code Map, Debugger Map and binary functionality.
  • The Debugger has one interesting upgrade: debugging is now supported for x86 applications built in .NET Native. .NET Native, released as a developer preview in April, is a compiler that strikes a compromise between the performance of C++ native code and the efficiency of C# managed code. The first release of .NET Native only supported x64 architecture.

Microsoft believes that smaller updates that come out more often are advantageous to developers. "Knowing that people are picking it [Visual Studio] up in a timely manner and starting to use it validates our theory that we need to be getting more things out to our customer base faster," Somasegar said in a previous interview.

It appears that no other major product in the Microsoft line is updated as quickly as Visual Studio:

  • Visual Studio 2013: Oct. 18, 2013
  • Release Candidate 1, Update 1: Dec. 9, 2103
  • Update 1: Jan. 20
  • Update 2: May 12
  • Update 3, CTP 1: May 22

Update 2 was a much bigger upgrade than Update 1, accounting for the four month gap between releases. Although Microsoft didn't specify a timetable for the official release of Update 3, it's likely to be shorter than the interval between Update 1 and Update 2 because of its more minor nature.

About the Author

Keith Ward is the editor in chief of Virtualization & Cloud Review. Follow him on Twitter @VirtReviewKeith.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube