Code Analysis Team Blog

As mentioned previously here and elsewhere, we're planning to improve and simplify several aspects of FxCop's extensibility model. This is the first of a series of threads about those improvements, in order to solicit feedback and give custom rules developers...

XSL authors out there have surely noticed that FxCop's report XML is extremely hierarchical and has relationships expressed in it that aren't relevant to most presentation purposes. So, we've simplified the XML greatly. Here's a breakdown of how targets...

This morning @ Teched, Steve Ballmer announced “Microsoft Visual Studio 2005 Team System“. Definately something for users of both VS & FxCop to take a look at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvsent/html...

As John MacKenzie pointed out on the GotDotNet FxCop message board , John Robbins has a great article in the June issue of MSDN magazine on FxCop 1.30 and custom rules using the new Introspection engine. Check it out at http://msdn.microsoft.com/msdnmag...

As the “Visual Studio 2005 Community Technology Preview March 2004” of the next release of the .NET framework (codename “Whidbey”) has been made available to customers recently. We expect people to want to analyze their projects...

Hi All, We just released FxCop 1.30! Please visit http://www.gotdotnet.com/team/fxcop/ to download it. main features: -No more locks on assemblies or pdbs -Ability to resolve missing dependencies -Ability to analyze just about anything running...

... goin' to California......

Just a heads up that FxCop 1.30 testing is right on track and we expect to ship on http://www.gotdotnet.com/team/fxcop by the end of this month, March 2004, as expected!

Craig Murphy will be doing a presentation on FxCop for the Scottish Developers User Group on Wednesday Feb. 25. He will be providing an overview of FxCop and the .NET Design Guidelines using C# and Delphi 8. More information can be found here: http...

We recently received a question regarding why FxCop violations occur against itself. This topic has already been partly covered by http://weblogs.asp.net/fxcop/archive/2004/01/08/48853.aspx but since there are a few FxCop-specific details for this variant...

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

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

For the (real) inaugural post, Michael Fanning explains why some shipped Microsoft managed assemblies have fxcop violations, a very good question. It's also a good insight into how we use FxCop internally at MS. -----Original Message----- From:...

Hello and welcome to the FxCop Team Blog! One of our team resolutions for this year (besides just trying to be generally nicer people) is to start an FxCop blog so here it is! Our goal is a single URL where we serve up tips and information about the FxCop...