Reporting Code Analysis Defect Counts

re: Reporting Code Analysis Defect Counts

David M. Kean — Mon, 11 Feb 2008 19:49:33 GMT

Andy,

> Is the code metrics tool going to be made available in VS Pro Edition? (VS 2008 of course)

No, there is no plans to push Code Metrics into the Pro edition.

re: Reporting Code Analysis Defect Counts

andeezle — Sun, 10 Feb 2008 21:56:22 GMT

Hi,

Is the code metrics tool going to be made available in VS Pro Edition? (VS 2008 of course) If not, it damn well ought to be. Just becuase I'm not working on a team doesn't make me any less important.

-Andy

re: Question: Displaying Code Analysis Results

George — Wed, 30 Jan 2008 03:30:33 GMT

Thanks for the reply Conor. We will just work with the current functionality and will look forward to the improved error reporting.

Cheers,

George

re: Reporting Code Analysis Defect Counts

conorm — Wed, 23 Jan 2008 05:00:29 GMT

Thanks for your suggestions George. We are looking in to improving the error reporting in the next release of Visual Studio and will bear this in mind.

To answer your question: you are not missing anything in 2005. We improved the reporting to tell you which projects were not in compliance in the 2008 version but still this is not to the individual error level. In VSS 2008 We also enabled a feature to allow you to merge in the policy settings with your local project settings which makes it really easy to get in compliance.

Hope this helps

Conor.

Question: Displaying Code Analysis Results

George — Wed, 23 Jan 2008 04:37:59 GMT

I have added custom code rules (in VS2005). These fire as a Check-in policy. But when a code rule is broken and I try to check in. The check in window (under the Policy Warnings) says "Project XYZ rule settings are not in conformance with Code Analysis policy".

I would like to double/right click on that and show the actual list of errors/warnings.

It should populate the "Error List" window with the results from the Code Analysis.

Can you please tell me if this is currently possible (ie am I missing a setting or something?) or if this feature will be added in a future release?

Thanks,

George

re: Reporting Code Analysis Defect Counts

abe — Sun, 06 Jan 2008 21:57:04 GMT

Including code analysis summary results in the build summary report - similar to Cruisecontrol would be nice

VSTS Links - 01/04/2008

Team System News — Fri, 04 Jan 2008 17:05:36 GMT

The Visual Studio Code Analysis Team Blog on Reporting Code Analysis Defect Counts. Mike Azocar on New...

re: Reporting Code Analysis Defect Counts

conorm — Thu, 03 Jan 2008 19:40:03 GMT

Nicole: thanks for your comments. I have read your blog posts on backlog cleanup and there are a lot of good ideas there. I am using some of that information as we design new features in code analysis for a future release.

re: Reporting Code Analysis Defect Counts

Nicole Calinoiu — Thu, 03 Jan 2008 17:23:44 GMT

In cases where warnings/errors are expected (e.g.: slow clean-up of a code analysis backlog), being able to group on rule category and/or rule would be useful.

Statistics concerning message suppressions (groupable by scope) would also be quite helpful since they would allow one to identify potentially troublesome patterns in exclusion vs fix activities.

MSDN Blog Postings » Reporting Code Analysis Defect Counts

MSDN Blog Postings » Reporting Code Analysis Defect Counts — Wed, 02 Jan 2008 23:39:02 GMT

PingBack from http://msdnrss.thecoderblogs.com/2008/01/02/reporting-code-analysis-defect-counts/