Some information on code analysis from the team’s blog. Old one but still pretty useful read…
With the launch of the Beta we would like to tell you about some of the great enhancements we have made to code analysis based on your feedback. Back when we started planning for Visual Studio 2012 we spent a good deal of time talking with people who use code analysis, and understanding the common pain points. What we learned was there are three key areas you would like to see us improve:
- Help better manage large numbers of warnings
- Make the output from the analyzer more understandable
- Improve the accuracy of the analyzer and the types of coding errors it finds
In this post let’s go over some of the highlights for code analysis in Visual Studio 2012:
- Code Analysis is available in all editions of Visual Studio and supports 64bit C++ projects
- Custom rule sets for C++ projects and quick keyword filtering for managing results
- Ability to step through each line on the warning path to improve understanding of the issue
- More accurate, relevant warnings to find important bugs early in development
Code Analysis Available in All Editions of Visual Studio
First, we are really excited to announce that we are including code analysis in all editions of Visual Studio 2012, including a subset of the most critical warnings in the Express edition for free (this applies to C++, C#, and VB code analysis) and all rules in the Professional, Premium, and Ultimate editions. We see code analysis as an important tool for writing high quality software, and we want you to have access to the same tools that we run internally at Microsoft.
Filtering and C++ Rule Sets
Historically, one of the difficult things about using code analysis has been managing the sometimes large sets of results. When we would run analysis on a moderate or large codebase for the first time the sheer number of warnings returned was overwhelming. Finding ways to carve off small bits was difficult.