{"id":2823,"date":"2011-08-24T20:40:00","date_gmt":"2011-08-24T20:40:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/vcblog\/2011\/08\/24\/first-look-at-the-new-c-ide-productivity-features-in-visual-studio-11\/"},"modified":"2021-10-11T15:55:28","modified_gmt":"2021-10-11T15:55:28","slug":"first-look-at-the-new-c-ide-productivity-features-in-visual-studio-11","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/first-look-at-the-new-c-ide-productivity-features-in-visual-studio-11\/","title":{"rendered":"First Look at the New C++ IDE Productivity Features in Visual Studio 11"},"content":{"rendered":"

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

Hi! I am Sumit Kumar<\/strong>, a Program Manager on the Visual C++ team.<\/p>\n

Today I will talk to you about some of the exciting new IDE functionality in the next version of Visual Studio<\/em> that will make you, the C++ developer, more productive with your daily code focused tasks. In this blog post you will get a preview of the new features that help with code understanding<\/i> and editing<\/i>. There will be more blog posts talking about other cool new features.<\/p>\n

 <\/p>\n

 <\/p>\n

Code Understanding enhancements<\/h2>\n

Semantic Colorization<\/h3>\n

Semantic Colorization<\/strong> helps you quickly scan the code and infer more semantic meaning through enhanced visual feedback in the editor. In addition to the keywords, strings and comments, now other tokens like types, enumerations and macros are colorized; the parameters are in italics and so on. The screenshot below shows an example. Notice how the macros, types, function parameters etc. pop out and make understanding code so much easier.<\/p>\n

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

While there are only a few tokens that are colorized differently by default, around twenty different semantic tokens are exposed to the users as shown in the screenshot below.<\/p>\n

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

You can customize your IDE to colorize these tokens differently. For example, you could choose to colorize local and global variables differently which could be a handy source understanding aid when the variables are identically named but defined in different scopes.<\/p>\n

 <\/p>\n

Reference Highlighting<\/h3>\n

Another great productivity feature that aids you in understanding code is Reference Highlighting<\/strong>. When you place your text cursor on a symbol, all the instances of that symbol in the file get highlighted. Only the true references are highlighted \u2013 for example, two symbols with same names in different scopes (say local vs. global) will not be highlighted at the same time. You can use Ctrl+Shift+Up<\/span> and Ctrl+Shift+Down<\/span> keys to move between the highlighted references. This means that you no longer have to invoke Find All References if you are simply looking for symbols within a file. The screenshot below shows how all the instances of the variable cxExtentMax<\/span> inside the function body are highlighted when the cursor is placed on the one referenced in the call to max()<\/span>. But the variable with same name defined outside the function scope is not highlighted.<\/p>\n

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

 <\/p>\n

New Solution Explorer<\/h3>\n

There are a number of tool windows needed for common everyday tasks \u2013 for example, Navigate To<\/span> is used for searching symbols and files, Class View<\/span> and Object Browser<\/span> are used for inspecting the members of an object, Find All References<\/span> is used for, well, finding references, Call Hierarchy<\/span> is used for finding the calls to and from a function etc. Imagine being able to do all of these operations from a single tool window without having to switch context or sacrifice additional precious screen real-estate. The new Solution Explorer<\/strong> combines most of the functionality of these tool windows into one place, itself! Of course, the other tool windows will still be available in Visual Studio, but the goal of the new Solution Explorer is to significantly reduce the need to invoke them for the most common scenarios. A detailed description of all of the new functionality provided by the versatile new Solution Explorer is a separate blog topic in itself, but here is a sampling:<\/p>\n

You can expand<\/b> your files to see the fields, functions and types contained in the files and the members contained in the types.<\/p>\n

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

It allows you to search<\/b> your entire solution all the way to the members of individual classes.<\/p>\n

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

You can navigate back and forward<\/b> between different views of the Solution Explorer and can create multiple instances<\/b> of Solution Explorer rooted at different nodes if needed. You can also scope<\/b> the view to just a specific project or file or type.<\/p>\n

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

The view in editor automatically syncs<\/b> with the view in Solution Explorer. Clicking on a symbol node in the Solution Explorer takes you to the definition of that symbol in the editor. You can also see the relationship between functions such as Calls to<\/span>, Calls from<\/span>, References<\/span>, and Inheritance<\/span> for functions and types from within the Solution Explorer.<\/p>\n

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

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

 <\/p>\n

 <\/p>\n

Code Editing enhancements<\/h2>\n

The second category of C++ features helps you with editing code faster.<\/p>\n

Automatic Display of IntelliSense Member List<\/h3>\n

In Visual Studio 2010 and previous releases, the IntelliSense member list dropdown had to be explicitly invoked either by typing Ctrl+Space<\/span> or Ctrl+J<\/span> or entering a scope resolution operator (::) or element selection operator (.<\/span> or -><\/span>). In the next version, Visual Studio will automatically shows the member list drop down<\/strong> as you type without the need to explicitly invoke it.<\/p>\n

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

The automatic display of member list is smart \u2013 it does not aggressively display the member list when it does not make sense, for example when typing a declaration, there is no aggressive display of member list.<\/p>\n

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

 <\/p>\n

Member List Filtering<\/h3>\n

Not only is the member list displayed automatically, it is also filtered as you type to shrink and show only the relevant members. So you can get a filtered result like the screenshot below just by typing two characters<\/p>\n

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

Notice that pb<\/span> is not a prefix or even a substring of the members in the list. The filtering uses a fuzzy logic to find the relevant members quickly. But if you do not like the fuzzy filtering, you can change it to prefix based, or prefix plus camel casing based or turn off the filtering completely.<\/p>\n

 <\/p>\n

Code Snippets<\/h3>\n

Code Snippets<\/strong> help you quickly type the boilerplate code with just a couple of keystrokes. Here\u2019s how it works for a switch statement: as you start typing, the IntelliSense member list shows you the relevant code snippet that can be selected by pressing tab.<\/p>\n

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

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

Then modify the expression in the switch statement or just press Enter<\/span> and the entire skeleton of the switch statement is added for you; you only need to fill in the logic!<\/p>\n

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

In addition to the switch<\/span> statement, there are other snippets for basic code constructs available to you \u2013 like if-else<\/span>, for<\/span> loop, etc. Each of the snippets saves you from unnecessary typing and lets you focus more on your logic, adding up to significant productivity gains over time!<\/span><\/p>\n

Additionally, the code snippets feature is extensible so you can also create your own snippets, which is as simple as creating a simple XML file and copying it at a certain location. You can also invoke the code snippets from the context menu in the editor and can either insert a snippet or can surround a selection of code with a code snippet (for example with a #ifdef<\/span> statement).<\/p>\n

 <\/p>\n

 <\/p>\n

Summary<\/h2>\n

Many of these code understanding and editing features were requested by you, and are squarely intended to make you more productive with C++ development. Your continued feedback will help us make these features better before they ship. Please note that the descriptions and screenshots are from our early internal builds. These features are still under development and could potentially change or not even be included in our final product<\/b>. In addition to these new features, we have done a lot of work on the IDE but I will save those for future blog posts.<\/p>\n

 <\/p>\n

[Keep learning about new features for C++ developers in Visual Studio 11]<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Hi! I am Sumit Kumar, a Program Manager on the Visual C++ team. Today I will talk to you about some of the exciting new IDE functionality in the next version of Visual Studio that will make you, the C++ developer, more productive with your daily code focused tasks. In this blog post you will […]<\/p>\n","protected":false},"author":289,"featured_media":35994,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[89,6,14],"class_list":["post-2823","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cplusplus","tag-editor","tag-ide","tag-intellisense"],"acf":[],"blog_post_summary":"

Hi! I am Sumit Kumar, a Program Manager on the Visual C++ team. Today I will talk to you about some of the exciting new IDE functionality in the next version of Visual Studio that will make you, the C++ developer, more productive with your daily code focused tasks. In this blog post you will […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/2823","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\/289"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=2823"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/2823\/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=2823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=2823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=2823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}