Code Analysis Team Blog

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...

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...

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...

A little known feature of FxCop (in particular FxCopCmd.exe) is its ability to be integrated into the build process within Visual Studio. Although not a replacement for the Code Analysis functionality available within both Visual Studio Team Edition for...

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...

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...

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...

One of my favorite new features for Code Analysis in Visual Studio 2008 is our support for analyzing anonymous methods and lambda expressions. While anonymous methods have been around in C# since Visual Studio 2005, lambda expressions are new for both...

While we've already briefly spoken about Code Metrics when we announced it , I thought I would discuss it in a little more depth, in particular the metrics it provides. As mentioned previously, Code Metrics is a new tool window that helps users find...

Announcing the new Code Metrics feature for Visual Studio ‘Orcas’! Available in Visual Studio Team Developer and Team Suite, this new feature allows users to generate code metrics for projects and solutions and displays the results in the Code Metrics...

DoNotExposeGenericLists fires when I publicly expose List<T> via a field, method, property, or parameter. Why? Although Krzysztof briefly touched on this last year , we wanted to expand on this a little through the use of examples. The first...

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...

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...

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...

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...

I've recently received a few requests asking about the Code Analysis rules we run internally against Microsoft's own code. While it might come as a surprise, we do not actually run every single rule against our own binaries. There are many reasons for...

Once you turn on the new spelling rules that we've added to Visual Studio 2008, you will want to start to customize the words that it fires on; this is where the new custom dictionary support comes in. A custom dictionary in its basic form, similar to...

This is the first installment in a three-part series on why FxCop warns against catch(Exception): FAQ: Why does FxCop warn against catch(Exception)? - Part 1 FAQ: Why does FxCop warn against catch(Exception)? - Part 2 FAQ: Why does FxCop warn against...

Update: To have rules target both Visual Studio and FxCop, see the following entry: FAQ: Can I create custom rules that target both Visual Studio and FxCop? Although not officially supported or documented, the Managed Code Analysis (FxCop) feature...

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...

FxCop 1.35 brings with it the ability to suppress messages in code via the use of the SuppressMessage attribute. This allows you to do the following: public class PublicKey { private byte [] _Token; [...] [SuppressMessage( "Microsoft.Performance" ...

As mentioned in previous blog and bulletin board posts, we’re in the final weeks of testing a new update to FxCop. This is a very significant update and I thought I’d post some information on what to expect in the release. No more locks...

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...

Two common questions we often get are: Can I write my own rules for FxCop and customize existing rules? Can I integrate FxCop into visual studio and can I jump to the location in my source of the item that FxCop flags as an error? That's why...

We are pleased to announce the release of FxCop 1.35. Please visit http://www.gotdotnet.com/team/fxcop to download it. Changes since FxCop 1.32: FxCop now only runs on .NET Framework 2.0, however, it supports analyzing all versions of .NET...