C++ Team Blog

The latest in C++, Visual Studio, VS Code, and vcpkg from the MSFT C++ team

Announcement - C++ Team Blog

Binary Compatibility and Pain-free Upgrade: Why Moving to Visual Studio 2017 is almost “too easy”

March 7, 2017 Mar 7, 2017 03/7/17
Marian Luparu
Visual Studio 2017 is a major leap forward in terms of C++ functionality compared with VS 2015. We hope the new release will delight you in your day-to-day job as soon as you can upgrade. This blog post focuses on the steps needed to upgrade from Visual Studio 2015 to 2017. As promised in our BUILD 2016 talk "6 reasons to move your C++ code ...

CMake support in Visual Studio 2017 – what’s new in the RC.2 update

December 20, 2016 Dec 20, 2016 12/20/16
Marian Luparu
In case you missed the latest Visual Studio news, there is a new update for Visual Studio 2017 RC available. You can either upgrade your existing installation or, if you’re starting fresh, install it from the Visual Studio 2017 RC download page. This release comes with several enhancements in Visual Studio’s CMake experience that further ...

Visual Studio 2017 RC Now Available

November 16, 2016 Nov 16, 2016 11/16/16
Eric Battalio
Visual Studio 2017 RC (previously known as Dev "15") is now available. There is a lot of stuff for C++ to love in this release: For more details, visit What's New for Visual C++ in Visual Studio 2017 RC. Going Native over on Channel 9 also has a good overview including a look at VCPkg. We thrive on your ...

Introducing the Visual Studio Build Tools

November 16, 2016 Nov 16, 2016 11/16/16
Adam Welch (MSFT)
Download the VS 2017 Build Tools (for C++ or managed code) Recap of the Visual C++ and Build Tools Last year we introduced the Visual C++ 2015 Build Tools to enable a streamlined build-lab experience for getting the required Visual C++ tools without the additional overhead of installing the Visual Studio IDE.  We expanded the options to ...

Find All References re-designed for larger searches

November 16, 2016 Nov 16, 2016 11/16/16
Augustin Popa
Visual Studio 2017 comes packed with several major changes to the core developer productivity experience. It is our goal to maximize your efficiency as you develop applications, and this requires us to constantly refine our features and improve on them over time. For Visual Studio 2017, we wanted to improve code navigation, particularly for ...

Introducing Go To, the successor to Navigate To

November 16, 2016 Nov 16, 2016 11/16/16
Augustin Popa
Visual Studio 2017 comes packed with several major changes to the core developer productivity experience. It is our goal to maximize your efficiency as you develop applications, and this requires us to constantly refine our features and improve on them over time. For Visual Studio 2017, we wanted to improve code navigation, particularly for ...

Open any folder with C++ sources in Visual Studio 2017 RC

November 16, 2016 Nov 16, 2016 11/16/16
Marian Luparu
With the Visual Studio 2017 RC release, we're continuing to improve the "Open Folder" capabilities for C++ source code. In this release, we're adding support for building as well as easier configuration for the debugger and the C++ language services. If you are just getting started with "Open Folder" or want to read about these capabilities ...

CMake support in Visual Studio – the Visual Studio 2017 RC update

November 16, 2016 Nov 16, 2016 11/16/16
Marian Luparu
Visual Studio 2017 RC is an important release when it comes to its support for CMake. The "Tools for CMake" VS component is now ready for public preview and we’d like to invite all of you to bring your CMake projects into VS and give us feedback on your experience. For an overview of the general Visual Studio CMake experience, head over to ...

Updates to Expression SFINAE in VS 2017 RC

November 16, 2016 Nov 16, 2016 11/16/16
Andrew Pardoe
Throughout the VS 2015 cycle we've been focusing on the quality of our expression SFINAE implementation. Because expression SFINAE issues can be subtle and complex we've been using popular libraries such as Boost and Microsoft's fork of Range-v3 to validate our implementation and find remaining bugs. As we shift the compiler team's focus to ...