Code Analysis Team Blog

Hi Everyone, 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...

  Recently we have received several questions regarding Visual Studio Code Analysis integration with Team Foundation Server’s check-in policy and build server, so I thought it would be helpful to clarify the behavior and expose some relatively hidden...

Version 10.0 of FxCop is the version that ships with Visual Studio 2010 Premium. FxCop 10.0 is part of Version 7.1 of the Microsoft Windows SDK for Windows 7 and .NET Framework 4. Instructions Download the Microsoft Windows SDK for Windows 7 and .NET...

This blog post applies to Visual Studio 2010 Premium and Ultimate editions. The content was written by Kevin Blasko one of the developers on the Visual Studio Code Analysis team. The purpose of this blog post is to give you some background on the implementation...

This blog explains how to implement your own static code analysis rules for analyzing your .NET (C#, VB.NET, etc) code. The material was written by Todd King, one of the developers on the Visual Studio Code Analysis team.   NOTE: Writing custom FxCop...

This blog compares the Code Analysis warnings and errors generated by Visual Studio 2008 and Visual Studio 2010.   Managed Code Analysis   Warning / Error Number Description Visual Studio 2008 Team System Visual Studio 2010 Premium CA0001 An...

This post summarizes the new functionality you will experience sing the Code Analysis functionality in Visual Studio 2010. Note that Code Analysis is only available in the Premium and Ultimate editions of Visual Studio 2010. Rule Sets In Visual Studio...

Two weeks ago, I introduced you to Visual Studio 2010 September '08 CTP (Community Technology Preview). This CTP is available as a Virtual PC (VPC) image which can be downloaded at http://go.microsoft.com/fwlink/?LinkId=129231 . The goal of the Community...

I've just published a post over my blog about a new feature we added for Visual Studio 2008 SP1 and FxCop 1.36. New for Visual Studio 2008 SP1 and FxCop 1.36 – Multi-targeting rule

We are pleased to announce that we've released the next version of FxCop . This release has a number of changes since FxCop 1.36 Beta 2, including, but not limited to, the following: Bug fixes that reduce noise, missing analysis and rule crashes...

For those that are interested, I've just started a new personal blog, Dave's Box , where I will be talking about FxCop, Framework Design Guidelines, and the recently announced Managed Extensibility Framework . I've just posted a couple of posts detailing...

We've just uploaded FxCop 1.35 to MSDN Code Gallery after we lost our home on GotDotNet - this is for those teams that either do not want to or just aren't ready to upgrade to FxCop 1.36 Beta . For those that are already using FxCop 1.35, you'll probably...

I've upgraded from FxCop 1.35 to 1.36 and now FxCop has started to fire warnings against typed DataSets and other generated code. How do I turn this off? The reason this is occurring is because we changed the way that FxCop analyzed generated code. Whereas...

Update: You can now download FxCop 1.35 directly from MSDN Code Gallery . As you many you have well noticed, GotDotNet was officially retired last month now that the last of its functionality was superceded by MSDN Code Gallery . Unfortunately, at...

Jason Kresowaty has posted a great tutorial on writing Code Analysis/FxCop rules . He also spends time on explaining parts of the Introspection API, including the different nodes and their relationship to each other. It's a great read, even if you...

Krzysztof and Brad have announced they are working on the second edition of the awesome Framework Design Guidelines and are looking for feedback on what they should put in it. For those that don't know, a lot of our Code Analysis rules are based on...

In response to a lot of recent requests, we've put together a complete list of rules that shipped in the different versions of Visual Studio Code Analysis and FxCop. Attached is an Excel worksheet providing this information for Visual Studio 2005, Visual...

Code analysis defect counts are available in the cube that is part of the TFS Data Warehouse . This post shows you how to hook up Excel to show code analysis counts in a pivot table . First off you need to connect Excel up to the data warehouse that has...

Join members of the Visual Studio Team System product group to discuss features available in Team Foundation Server, Team Suite, Architecture Edition, Development Edition, Database Edition, and Test Edition. In addition, discuss what's new for these editions...

We have a great new feature that we are previewing in Microsoft® Visual Studio® Team System code name “Rosario” November 2007 CTP .  This feature allows you to select pre-defined sets of rules to configure code analysis as well...

Another question that is coming up is: How can (or should) code metrics be presented to management ? My view is that in all cases the metrics are something that can help make decisions around focus and prioritization. Management should be made aware of...

Another question: The maintainability index has been re-set to lie between 0 and 100. How and why was this done? The metric originally was calculated as follows: Maintainability Index = 171 - 5.2 * ln(Halstead Volume) - 0.23 * (Cyclomatic Complexity...

This is the first in a series of posts around questions I am getting asked related to code metrics. One question that is coming up is: Can a check-in policy be defined based on code metrics in TFS? Well, code metrics itself does not have a check...

A number of people have asked: Is there a way to customize the existing code metrics or add additional ones? The simple answer at this time is No.  There are no extension points or customizations available at this time for code metrics.  This...

I'm pleased to announce that we've released a beta of the next version of FxCop . This release has a number of changes since FxCop 1.35, including, but not limited to, the following: 200+ bug fixes that reduce noise, missing analysis and rule crashes...