{"id":18105,"date":"2018-01-10T12:39:49","date_gmt":"2018-01-10T20:39:49","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/vcblog\/?p=18105"},"modified":"2019-02-18T17:48:06","modified_gmt":"2019-02-18T17:48:06","slug":"c-static-analysis-improvements-for-visual-studio-2017-15-6-preview-2","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/c-static-analysis-improvements-for-visual-studio-2017-15-6-preview-2\/","title":{"rendered":"C++ Static Analysis Improvements for Visual Studio 2017 15.6 Preview 2"},"content":{"rendered":"

\u70b9\u8fd9\u91cc\u770b\u4e2d\u6587\u7248<\/a> <\/p>\n

We’ve made a few changes to the C++ static analysis feature that should make it faster and easier to use. The behavior has changed slightly, and the menus have been moved around a bit, but we think that the new experience is faster and more consistent. Let’s take a quick look at the changes.<\/p>\n

Single File Analysis<\/h2>\n

Developers tend to focus on a few files at a time when working on code. To make it easier to get analysis results for the files you’re editing, you can now run code analysis on a single file. This lets you get code analysis warnings without having to rebuild the entire project. We think this will be especially useful when fixing analysis warnings because it makes it convenient to check and recheck a file. After analysis runs, all analysis warnings for the file will appear in the error list.<\/p>\n

\"Screenshot<\/a>
New build menu item to run C++ code analysis on a single file.<\/figcaption><\/figure><\/p>\n

 <\/p>\n

\"Screenshot<\/a>
Code Analysis results for a single file.<\/figcaption><\/figure><\/p>\n

If you have a few files you want to check, you can also select multiple files in the Solution Explorer and run code analysis on only those files.<\/p>\n

\"Screenshot<\/a>
Multiple files selected in the Solution Explorer can be analyzed at once.<\/figcaption><\/figure><\/p>\n

More Consistent Menus<\/h2>\n

To make the code analysis menus easier to find, we’ve made them more consistent with their \u201cBuild\u201d counterparts. In previous versions, you would find the menu to run code analysis on a project under the “Project Only” menu. Now the menus to start analysis on a solution, project, or file are located near their “Build X” counterpart on the “Build” menu. On the Solution Explorer context menus, look for the “Analyze” menu on the solution, project, and file nodes of the tree.<\/p>\n

Build Menu<\/h3>\n

\"Screenshot<\/a>
New build menu locations for starting solution, project, and per-file code analysis.<\/figcaption><\/figure><\/p>\n

Context Menus<\/h3>\n

\"Screenshot<\/a>
New Solution Explorer context menus for running solution, project or per-file code analysis.<\/figcaption><\/figure><\/p>\n

Analyze Only<\/h2>\n

We’ve heard from developers that running code analysis takes too long. In previous versions, running code analysis required a full build and link before analysis would run. Now when you run code analysis, we no longer generate code or link. This dramatically reduces analysis run time.<\/p>\n

One side effect is that you will no longer see some build warnings during analysis runs. You will get build warnings during builds, and code analysis warnings during analysis runs. If you prefer to see build and analysis warnings at the same time, check the “Enable Code Analysis on Build” box in the project properties and rebuild your project.<\/p>\n

\"Screenshot<\/a>
Enable Code Analysis on Build to get build and analysis results at the same time.<\/figcaption><\/figure><\/p>\n

C++ Core Guidelines Checker<\/h2>\n

C++ Core Check is currently not enabled by default, so if you want to try out the new single-file analysis experience with C++ Core Check, the extension must first be enabled on the project.<\/p>\n

\"Screenshot<\/a>
The C++ Core Check extension has to be enabled per-project if you want the C++ Core Check results when you run code analysis.<\/figcaption><\/figure><\/p>\n

Wrap Up<\/h2>\n

These are just a few simple tweaks to improve the C++ code analysis experience. Download the latest Visual Studio preview<\/a> and give them a try. We hope you will find it easier to use on your projects and that the tools help you write safer, more modern C++.<\/p>\n

As always, we welcome your feedback. Feel free to send any comments through e-mail at visualcpp@microsoft.com<\/a>, through Twitter @visualc<\/a>, or Facebook at Microsoft Visual Cpp<\/a>.<\/p>\n

If you encounter other problems with MSVC in VS 2017 please let us know via the Report a Problem<\/a> option, either from the installer or the Visual Studio IDE itself. For suggestions, let us know through UserVoice<\/a>. Thank you!<\/p>\n

Happy coding.<\/p>\n","protected":false},"excerpt":{"rendered":"

\u70b9\u8fd9\u91cc\u770b\u4e2d\u6587\u7248 We’ve made a few changes to the C++ static analysis feature that should make it faster and easier to use. The behavior has changed slightly, and the menus have been moved around a bit, but we think that the new experience is faster and more consistent. Let’s take a quick look at the changes. […]<\/p>\n","protected":false},"author":2869,"featured_media":35994,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[270],"tags":[245,163],"class_list":["post-18105","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcement","tag-cppcorecheck","tag-static-analysis"],"acf":[],"blog_post_summary":"

\u70b9\u8fd9\u91cc\u770b\u4e2d\u6587\u7248 We’ve made a few changes to the C++ static analysis feature that should make it faster and easier to use. The behavior has changed slightly, and the menus have been moved around a bit, but we think that the new experience is faster and more consistent. Let’s take a quick look at the changes. […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/18105","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\/2869"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=18105"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/18105\/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=18105"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=18105"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=18105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}