0.12.2

• Added a gcc problemMatcher. #854
• Fix a crash with the IntelliSense process (responsible for ~25% of all crashes).
• Fixes for language server issues #325, #884, #886, #888, #906, microsoft/vscode#27404

0.12.1

July 2017 Update

• Fix Tag Parser features not working with some MinGW library code.
• Fix a symbol search crash.
• Fix an IntelliSense engine compiler crash.
• Fix Go to Declaration to return Go to Definition results if the declarations have no results.
• Fixes for language server issues: #870, #872, #875,
• Deprecate addWorkspaceRootToIncludePath setting and instead make ${workspaceRoot} in browse.path explicit.
• Add Show Release Notes command.
• Add Edit Configurations... command to the Select a Configuration... dropdown.
• Update Microsoft Visual C++ debugger to Visual Studio 2017 released components.
  • Fix issue with showing wrong thread. #550
  • Fix issue with binaries compiled with /FASTLINK causing debugger to hang. #484
• Fix issue in MinGW/Cygwin debugging where stop debugging causes VS Code to hang. microsoft/MIEngine#636

0.12.0

June 2017 Update

• The default IntelliSense engine now provides semantic-aware autocomplete suggestions for ., ->, and :: operators. #13
• The default IntelliSense engine now reports the unresolved include files in referenced headers and falls back to the Tag Parser until headers are resolved.
  • This behavior can be overridden by setting "C_Cpp.intelliSenseEngineFallback": "Disabled"
• Added "C_Cpp.intelliSenseMode" setting to allow switching between MSVC and Clang modes. #710, #757
• A crashed IntelliSense engine no longer gives the popup message, and it automatically restarts after an edit to the translation unit occurs.
• Fix the IntelliSense engine to use "c" mode if a C header is opened before the C file.
• Fix a bug which could cause the IntelliSense engine to not update results if changes are made to multiple files of a translation unit.
• Auto files.association registers "c" language headers when Go to Definition is used in a C file.
• Downloading extension dependencies will retry up to 5 times in the event of a failure. #694
• Changes to c_cpp_properties.json are detected even if file watchers fail.
• Update default IntelliSense options for MSVC mode to make Boost projects work better. #775
• Fix Go to Definition not working until all browse.path files are re-scanned. #788

0.11.4

• Fixed a blocking debugger issue on Linux #792

0.11.3

• fixed a bug with automatic population of includePath on Linux/Mac

0.11.2

Enabling the new IntelliSense engine by default for everyone turned out to be disruptive for a lot of our users, so we are disabling it by default for non-Insiders while we work on a better migration experience.

We appreciate the time everyone has taken to provide feedback.

0.11.1

This update improves the debugger setup experience by adding new commands to the command palette and configuration snippets for launch.json.
More detail about these features can be found here.

Based on the telemetry received from our customers using the new IntelliSense engine on the Insider build as well as those who opted in, we decided to enable it by default for all VS Code users.

We committed fixes for the following language server issues: #120, #546, #604, #606, #648, #656, #662, #666, #673, #685, #691, #699

0.11.0

In this release we are making available a preview of the first few features supported by the new IntelliSense engine. You can check out the feature by changing the C_Cpp.intelliSenseEngine setting to Default in your settings.json file. We describe the features currently implemented in more detail here.

We know the results of the IntelliSense engine aren't perfect (that's why this feature is in preview), so we would appreciate your feedback on the experience so we can prioritize the issues and make it better for everyone.

An important thing to note is that we have changed the meaning of the includePath setting in your c_cpp_properties.json file. The includePath setting now controls the (non-recursive) paths that are used by IntelliSense when parsing your files. The old (recursive) paths you used to set for includePath are being moved to the browse.path setting. When you open a folder in VS Code, we will copy your existing includePath setting to the browse.path setting if the browse.path setting is non-existent. If you don't have a c_cpp_properties.json file for your folder, we will pick a default set of folders as described in the blog post linked above.

We also committed fixes for the following language server issues: #23118, #485 #584, #586, #591, #593, #608, #611, #625, #630, #641, #650, #653, #654

0.10.5

In this update we reverted a change we made in v0.10.4 which globally set language specific overrides for the editor.quickSuggestions setting (Issue #572). The change in v0.10.4 resulted in an unexpected regression for developers using our extension in conjunction with another extension that provides auto-complete suggestions. Instead, in v0.10.5 we will add this setting to a developer’s settings.json file if the C_Cpp.autocomplete setting is set to Default and remove it (if applicable) when a developer changes this setting to Disabled.

It is important to note, however, that a bug in the current stable version of VS Code (1.10.2) does not automatically refresh the settings.json file at the time the C_Cpp.autocomplete setting changes values. To avoid getting a merge conflict in your settings.json file in VS Code, we recommend you close and reopen the settings.json file after making any changes to the C_Cpp.autocomplete setting. The insider build of VS Code does not exhibit this bug, so we expect it to be fixed in the stable build shortly.

We also fixed a memory corruption bug reported in issue #430
We fixed some issues around missing symbols on Linux/Mac stdlib.h functions. #578
We made additional fixes for switch header/source not respecting files.exclude. #485