{"id":16356,"date":"2017-07-18T16:29:06","date_gmt":"2017-07-18T23:29:06","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/vcblog\/?p=16356"},"modified":"2019-02-18T17:48:24","modified_gmt":"2019-02-18T17:48:24","slug":"visual-studio-code-cc-extension-july-2017-update-time-to-try-out-the-new-intellisense","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/visual-studio-code-cc-extension-july-2017-update-time-to-try-out-the-new-intellisense\/","title":{"rendered":"Visual Studio Code C\/C++ extension July 2017 Update \u2013 time to try out the new IntelliSense!"},"content":{"rendered":"

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

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<\/a> and off for everyone else, but we encourage everyone to try out the new, improved IntelliSense!<\/strong> You will get improved, more accurate results for several IntelliSense features, including auto-complete suggestions for class\/struct\/namespace members<\/strong>, quick info tooltips<\/strong>, and error squiggles<\/strong> (linting), all powered by a new semantic engine. You can turn on the new IntelliSense by changing the \u201cC_Cpp.intelliSenseEngine\u201d setting in your settings.json <\/em> file (open from menu File->Preferences->Settings<\/em>) from \u201cTag Parser\u201d to \u201cDefault\u201d, as shown in the screenshot below.<\/p>\n

\"\"<\/a>The following screenshot shows auto-complete suggestions for a class and quick info tooltips using the new IntelliSense engine.<\/p>\n

\"\"<\/a><\/p>\n

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<\/a> details how the fallback behavior works and how you can control it.<\/p>\n

Tell us what you think<\/h2>\n

We encourage everyone to try out the new IntelliSense and send us feedback. Download the C\/C++ extension for Visual Studio Code<\/a>, try it out and let us know what you think. File issues and suggestions on GitHub<\/a>. If you haven\u2019t already provided us feedback, please take this quick survey<\/a> to help shape this extension for your needs.<\/p>\n","protected":false},"excerpt":{"rendered":"

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 […]<\/p>\n","protected":false},"author":269,"featured_media":35994,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[270,275],"tags":[274,276],"class_list":["post-16356","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcement","category-visual-studio-code","tag-c-extension","tag-vscode"],"acf":[],"blog_post_summary":"

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 […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/16356","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/users\/269"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=16356"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/16356\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/35994"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=16356"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=16356"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=16356"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}