News

Visual Studio 14 Update: CTP 4 Slims Down

Fourth in line of public previews comes with improvements to ASP.NET vNext, the Common Language Runtime, and C++ debugging and C# language constructs.

Microsoft earlier this week released the fourth community technology preview for its upcoming Visual Studio 14, this one with improvements mainly in ASP.NET vNext and .NET Framework, and some streamlining in C++ and C#.

It was nearly a month ago that CTP 3 was released with a preview of ASP.NET vNext and .NET Framework vNext. In the CTP 4 release, those features have started to take shape based on just several weeks of work and developer community feedback.

On the ASP.NET vNext side specifically, there's a few new ASP.NET tooling and Web development-related changes. One such change is the way "Visual Studio now uses a design-time host to speed up Visual Studio build scenarios for ASP.NET vNext projects," according to Visual Studio 14 Release Notes. The idea here is to shorten the process, as projects are built in memory even as changes are made.

ASP.NET vNext project templates have also gone through some improvements, specifically in its support for modern project layouts, and an alpha4 runtime package has been included as well.

The .NET Framework adds an updated version of RyuJIT, the 64-bit just in time compiler, which the support note says "provides significant performance improvements over the legacy 64-bit JIT compiler." The note also says to be aware that because of the changes to this version that there may be some lingering behavioral changes if used.

The CTP also comes with C++ debugging improvements, which are detailed in a separate post. Specifically, Microsoft's Andrew B. Hall writes of a new way to configure breakpoints and offers a demonstration of the new features of the Breakpoint Settings peek windows. He says the debugger also loads faster and is more capable of handling function deadlock issues.

The version of C# 6.0 also gets streamlined a bit, with primary constructors and declaration expressions getting cut from the language. The cuts will also effect some of the development with the .NET Compiler Platform (aka 'Roslyn'), and there's some discussion of it here on the Codeplex site. In short, there is too much "downstream work to be supported in the IDE, debugger,...." and other features to be able to make significant progress with the rest of the tools. (To read about C# 6.0 as it existed in Visual Studio 14 CTP3, see Mark Michaelis' review, "The New and Improved C# 6.0," on the MSDN Magazine Web site.)

To drill down on all the details of this release, which includes bugs and known issues and download requirements, see the Microsoft support document here.

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