David Kean’s new blog

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 changes we made to FxCop 1.36:  FxCop now ships with the spell checker librariesReference resolution changes in Code…


FxCop 1.35 now available (again) for download

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 notice that we flicked the switch to…


FAQ: How do I prevent FxCop 1.36 from firing warnings against generated code?

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 previously in 1.35, FxCop would only ignore particular generated code…


What happened to the download and documentation of FxCop 1.35?

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 the same time, the FxCop team page, the download for FxCop 1.35 and the rule documentation was…


Tutorial on writing your own Code Analysis rule

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’ve written some Code Analysis rules before. Definitely recommended.


What do you want to see in the second edition of Framework Design Guidelines?

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 the writings in this great book, so expect to see…


FAQ: Which Code Analysis rules shipped in which version?

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 Studio 2008, FxCop 1.35 and FxCop 1.36 Beta. One of things you’ll notice…


Reporting Code Analysis Defect Counts

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 the data. Under the Data tab…


Come chat with the Code Analysis team tomorrow

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 for Visual Studio 2008. We will be holding two sessions: Join the chat on Wednesday, December 5th, 2007…


Try the Code Analysis Rule Sets Feature in the November "Rosario" November 2007 CTP

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 as define your own.  To access this feature right click on a project and choose "Properties" then…