News

What's 'vNext'? It's Visual Studio "14" CTP 3

VS "14" CTP 3 includes early build of next-generation Microsoft .NET Framework and ASP.NET, plus a slew of enhancements that include C++ productivity improvements.

The Visual Studio team blogs of its third community technology preview (CTP) for Visual Studio "14," a version of which includes an early build of the next-generation versions of the Microsoft .NET Framework and ASP.NET, plus a slew of enhancements that include C++ productivity improvements. Related to the CTP 3, the team said that the Azure Resource Manager Tools and Bing Developer Assistant for Visual Studio were also released.

The highlight of Visual Studio 14 CTP 3 is the inclusion of the vNext versions of the .NET Framework and ASP.NET. The CTP 3 version of .NET vNext builds upon a version that was released in May along with the .NET Framework 4.5.2, but with a few more incremental changes, as well as a rollup of bug fixes. ASP.NET vNext includes "support for build configuration and support for unit tests, and it no longer includes content and compile items inside '.kproj' file," according the Visual Studio Team blog, and includes the RyuJIT compiler.

This CTP also includes .NET Native for the first time, which has some support for Windows Communication Foundation (WCF) so that services can be added natively through the .NET Native app. The blog lists a number of WCF types and target scenarios that are supported right now, and more will be forthcoming.

The RyuJIT compiler that comes with ASP.NET can be tested out, but it isn't natively supported from the .NET Framework vNext (the team said internal builds do have it working natively, but it isn't ready for external preview). The blog has instructions for testing it out, though, for those curious to try it.

Other enhancements include improved PerfTips in the debugger, support for high-resolution icons in command bars, tool bars and menus, roaming custom layouts, and enhancements to Visual C++ that allow it to conform to C++ standards in order to make working with the compiler more productive. One such improvement there is the replacement of Smart Tags with Light Bulbs, which the team deems "more discoverable" when glancing at code for fixes, and which actually show what resultant fixes will look like as a preview.

Also new is support for "thread_local storage specifier, which allows objects to be stored separately for each thread" from within the compiler. A number of other improvements are listed in a Visual C++ Team blog post.

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at [email protected].

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