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