News

New Visual Studio 2017 15.5 Preview Boosts C++ Functionality

Microsoft this week issued its second preview of Visual Studio 2017 15.5, with several new features introduced to improve C++ development in particular.

New C++ functionality in this second preview (read about new features in the first preview here) includes support for the C++ 17 standard being added to the Standard Template Library and the Visual C++ compiler.

According to the release notes, 13 different tweaks were made to the Standard Template Library to match up with C++ 17, ranging from deprecating several features to various fixes and other changes.

The compiler, meanwhile, received several of its own tweaks, so it now matches up with about 75 percent of the C++ 17 standard. Some of those include structured bindings, constexpr lambdas, if constexpr, inline variables, fold expressions, hexfloat literals, and the addition of noexcept to the type system.

Other C++ components were also improved, including the Visual C++ optimizer, the C++ Core Guidelines checker and the Test Explorer, which now has built-in default support for the Google Test framework.

Christine Ruana, principal program manager, Visual Studio, detailed these changes in a blog post yesterday.

"We're also shipping new C++ Core Guidelines checks in C++ code analysis, which will help ensure your C++ code is robust," Ruana said. "In this release the Test Explorer supports the Google Test Framework, which enables you to write, discover, and run your Google Test C++ unit tests from within the context of Visual Studio. Lastly, we've improved the Linux C++ Workload by introducing support for cross compilation targeting ARM microcontrollers and capabilities to run remote tasks."

Beyond those C++ enhancements, several other improvements were noted for TypeScript, JavaScript and more, including Angular 2 Support for inline and .ngml template files and the exapansion of the IntelliTrace step-back debugging feature to support debugging ASP.NET applications running in IIS Express.

Step-Back Debugging in Action
[Click on image for larger animated GIF.] Step-Back Debugging in Action (source: Microsoft).

Various bug fixes were also announced, along with an updated error dialog to provide more information about installation problems, with community help for problems being provided if it's available.

The VS team noted this release is not "go-live" and isn't intended for use on production computers or for creating production code. It is intended for testing and soliciting developer feedback, which can be sent in by clicking on the Report a Problem option in the upper right-hand corner of the installer or Visual Studio itself. Feature suggestions can be relayed via the UserVoice site.

"You'll be able to track your issues in the Visual Studio Developer Community where you can ask questions and find answers," "You can also engage with us and other Visual Studio developers through our Visual Studio conversation in the Gitter community (requires a GitHub account)."

About the Author

David Ramel is an editor and writer at Converge 360.

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