Windows 10: Visual Studio Code C/C++ extension June 2018 Update

Brink · Jun 22, 2018

Today we’re very happy to announce the availability of the June 2018 update to the C/C++ extension for Visual Studio Code! In this update, we are continuing our efforts to make IntelliSense configuration easier by auto-detecting compile_commands.json files for IntelliSense, significantly improving recursive search performance, making browse.path optional, and adding “compilerPath” support for MSVC.

IntelliSense auto-detects compile_commands.json

In this update, compile_commands.json files in the workspace will be detected to auto-configure IntelliSense, eliminating the need to manually specify includes and defines.

Compile_commands.json file is a compilation database that consists of an array of “command objects”, where each command object specifies one way a translation unit is compiled in the project. Its format is specified in the Clang documentation, and it can be generated by many build systems, such as CMake. The C/C++ extension added support for it in the October 2017 update, but it was an optional setting that required manually setting the path to the file. This latest update added auto-detection to make use of such files. If multiple files are found, you will be presented with a dropdown to choose the appropriate one. The following screenshot shows an example of the message suggesting the use of a compile_commands.json file to auto-configure IntelliSense and the dropdown with two choices.

Once selected, IntelliSense will be fully powered by using the information in that file with no further configuration required. If you need to change the path, you can find the “compileCommands” setting in the c_cpp_properties.json file (access via Command Palette -> C/Cpp: Edit Configurations…).

Performance improvement for IntelliSense path recursive search

Support for recursive search of “includePath” was added in the May 2018 update. This latest update significantly improves the search performance on large folders. By intelligently cutting down the number of paths that need to be processed by the IntelliSense engine, we were able to make search faster – in particular, subsequent folder opening is orders of magnitude faster. Due to these improvements, recursive search is now the default behavior for newly-opened folders. To opt out, simply remove “**” from each path in the c_cpp_properties.json file.

Browse.path is now optional

For the longest time, we had two path settings: “includePath” for the IntelliSense engine, and “browse.path” for the Tag Parser. The IntelliSense engines document explains the difference between the two. While it could be useful at times to have different sets of paths, in many cases they end up being duplicated. In this update, we’re making “browse.path” optional, which means it won’t be populated in newly-created c_cpp_properties.json files. The “includePath” values will be used for the Tag Parser in addition to the IntelliSense engine, if “browse.path” is not present.

compilerPath setting added support for MSVC (Microsoft Visual C++ Compiler)

“compilerPath” is a setting introduced previously that allows users to specify a compiler from which IntelliSense can retrieve system includes and defines. This update added support for MSVC – this means the “compilerPath” setting in the default Windows configuration will use the latest MSVC installed on the machine for includes and its value can be changed to a different version if needed.

Tell us what you think

Download the C/C++ extension for Visual Studio Code, try it out and let us know what you think. File issues and suggestions on GitHub. If you haven’t already provided us feedback, please take this quick survey to help shape this extension for your needs.
Click to expand...

Source: Visual Studio Code C/C++ extension June 2018 Update | Visual C++ Team Blog

:)

Brink · Jun 22, 2018

Visual Studio Code C/C++ extension March 2018 update

Today we are excited to announce the March 2018 update to the Visual Studio Code C/C++ extension! This update includes improved auto-complete for local and global scopes and a simplified configuration process for system includes and defines, enabling a better out-of-box IntelliSense experience. You can find the full list of changes in the release notes.

We’d like to thank everyone who tried our Insiders builds earlier this month and sent us feedback! Fixes for the issues you reported and feature suggestions you told us about helped shape the final release the way it is today. If you are not yet an insider but are interested, we’d love for you to join the VS Code C/C++ Insiders program.

Auto-complete for local and global scopes

While this feature is not completely new, IntelliSense now provides a semantic-aware list of auto-complete suggestions when you type in local and global variables and functions. Compared with the previous approach, the new auto-complete experience gives you a shorter and more relevant list of suggestions, making it easier to write C/C++ code.

System includes and defines automatically retrieved from the compiler

IntelliSense now automatically retrieves system includes and defines from GCC/Clang-based compilers, eliminating the need for manual configuration in the “includePath” and “defines” settings. On Mac and Linux, the IntelliSense engine automatically selects a compiler as the default by searching for the installed compilers on the system. You can check which compiler is being used in the new “compilerPath” setting in the c_cpp_properties.json file, and change the value if needed. The “compilerPath” setting also accepts compiler arguments that affect the system defines returned.

In addition, the new “cStandard” and “cppStandard” settings allow setting language standards explicitly for IntelliSense.

Force IntelliSense to process arbitrary headers

If you wish IntelliSense to process headers that are not explicitly listed in #include statements, you can now use the new “forcedInclude” setting to specify them. The IntelliSense engine will first process these headers before it looks at #includes.

Tell us what you think

Download the C/C++ extension for Visual Studio Code, try it out, and let us know what you think. File issues and suggestions on GitHub. If you haven’t already provided us feedback, please take this quick survey to help shape this extension for your needs. You can also find us on Twitter (@VisualC).
Click to expand...

Source: Visual Studio Code C/C++ extension March 2018 update | Visual C++ Team Blog

Brink · Jun 22, 2018

December Update for the Visual Studio Code C/C++ extension

At //Build this year we launched the C/C++ extension for Visual Studio Code. Keeping with the monthly release cadence and goal to continuously respond to your feedback, this December update introduces the following features:

Debugger visualizations by default with Pretty Printing for GDB users

Ability to map source files during debugging

If you haven’t already provided us feedback, please take this quick survey to help shape this extension for your needs. The original blog post has already been updated with these new feature additions. Let’s learn more about each one of them now!
Click to expand...

Read more: December Update for the Visual Studio Code C/C++ extension | Visual C++ Team Blog

Brink · Jun 22, 2018

Visual Studio Code C/C++ extension July 2017 Update

2 million downloads! This is very exciting for the Visual Studio Code C/C++ extension, considering it was just 4 months ago when we hit the 1 million milestone!

Today we are shipping the July 2017 update to the extension. Besides several bug fixes, we are continuing to polish the new IntelliSense experience that we shipped last month. This new experience continues to be on by default for VS Code Insiders and off for everyone else, but we encourage everyone to try out the new, improved IntelliSense! You will get improved, more accurate results for several IntelliSense features, including auto-complete suggestions for class/struct/namespace members, quick info tooltips, and error squiggles (linting), all powered by a new semantic engine. You can turn on the new IntelliSense by changing the “C_Cpp.intelliSenseEngine” setting in your settings.json file (open from menu File->Preferences->Settings) from “Tag Parser” to “Default”, as shown in the screenshot below.

The following screenshot shows auto-complete suggestions for a class and quick info tooltips using the new IntelliSense engine.

The extension enables the new IntelliSense experience by first trying to fully parse any opened file using the new IntelliSense engine. If it discovers that it cannot find a header file or a dependency, it will fall back to the tag parser and provide the original fuzzy IntelliSense behavior. This blog post Visual Studio Code C/C++ extension June 2017 Update details how the fallback behavior works and how you can control it.

Tell us what you think

We encourage everyone to try out the new IntelliSense and send us feedback. Download the C/C++ extension for Visual Studio Code, try it out and let us know what you think. File issues and suggestions on GitHub. If you haven’t already provided us feedback, please take this quick survey to help shape this extension for your needs.
Click to expand...

Source: Visual Studio Code C/C++ extension July 2017 Update - time to try out the new IntelliSense! | Visual C++ Team Blog

Windows 10: Visual Studio Code C/C++ extension June 2018 Update

Visual Studio Code C/C++ extension June 2018 Update

Visual Studio Code C/C++ extension June 2018 Update

Visual Studio Code C/C++ extension June 2018 Update

Visual Studio Code C/C++ extension June 2018 Update - Similar Threads - Visual Studio Code

C/C++ extension doesn't show up in Visual Studio Code extension manager search.

CANNOT FIND C/C++ EXTENSION ON VISUAL STUDIO

Visual Studio Code C/C++ extension July 2017 Update

Visual Studio Code C/C++ extension May 2017 Update

Visual Studio Code C/C++ extension April 2017 Update

Visual Studio Code C/C++ extension March 2018 update

December Update for the Visual Studio Code C/C++ extension

Python Extension for Visual Studio Code - March 2018 Release

Visual Studio Code C/C++ extension August 2017 Update

Users found this page by searching for:

c/cpp visual studio extension code format