FxCop and the big, bad backlog

A statistics collection tool for FxCop backlogs

I may have joined the wrong side — Fri, 15 Feb 2008 20:24:32 GMT

For the past week or so, I've been performing last-minute documentation tasks at the day job in preparation

re: FxCop and the big, bad backlog

calinoiu — Wed, 30 Jan 2008 13:10:18 GMT

Grant: We do apply the FxCop naming rules, but not "just to satisfy FxCop". The naming rules are based on the naming conventions from the .NET API design guidelines (msdn2.microsoft.com/.../ms229002.aspx), and following those guidelines can go a long way toward helping consumers of an API feel comfortable with its public interface.

re: FxCop and the big, bad backlog

Grant Palin — Fri, 25 Jan 2008 02:25:03 GMT

Some interesting ideas here. I recently started using FxCop on a project of mine, and have a good-sized initial backlog to deal with - 835 items, not sure how that compares with your situation...I recently wrote a post on my own blog on the basics of FxCop and using it with NAnt, so I am getting on my way.

I have been reading up on the various violations I keep getting, to learn how to deal with them. It will be a process, all right.

Something I am curious about, do you necessarily write code to FxCop's standards, as far as naming goes? I know there are many preferences are out there, and wondered if anyone tailored their code just to satisfy FxCop.

re: FxCop and the big, bad backlog

calinoiu — Sun, 09 Dec 2007 14:21:18 GMT

George: We briefly considered a similar approach but ended up rejecting it due to the sheer volume of our existing backlog*. I'm guessing that you probably started with a considerably smaller smaller backlog than ours, particularly since you mention that it was a "modest sized project", and I'm curious as to the initial size of your backlog and the rate of clean-up that you saw once the problem tracker was activated.

*The desire to provide training on any given rule before bulk clean-up of problems for that rule begins was also a factor in this decision, but it didn't carry as much weight as the backlog size issue.

FxCop

From the software development trenches — Fri, 23 Nov 2007 10:21:16 GMT

In previous posts about Code Metrics and Code Reviews , I explored some metrics and techniques that I

re: FxCop and the big, bad backlog

George Mills — Thu, 23 Aug 2007 20:37:59 GMT

We took care of the backlog via different approach.

We wrote a simple tool to count the number of errors on the output. If the count went up we fail the build. If the count goes down we pass the build and lower the max count allowed.

This allowed us to turn on ALL errors and not let new errors into the system while we try to remove existing errors. It worked great.

We also use the same tool to compare the # of projects found in the solution file and the fxcop project file. If they differ we fail the build. This way if someone adds project and forgets to add it to FxCop the build fails.

I posted this info on the FxCop forum but nobody seemed to even notice. To me this made it feasable to use FxCop in the middle of a modest sized project.

FxCop backlog tools: FxCop

I may have joined the wrong side — Sat, 02 Jun 2007 13:14:48 GMT

If you're considering tackling an FxCop backlog , you're going to need a few tools. Obviously

FxCop is case-sensitive. VB is annoying.

I may have joined the wrong side — Tue, 08 May 2007 03:34:39 GMT

With profound apologies to VB lovers, there are a few features of the VB compiler that occasionally make

FxCop backlog themes: Exceptions

I may have joined the wrong side — Sat, 05 May 2007 16:47:54 GMT

Since I started monitoring traffic on this blog a little more closely about a week ago, I had the unexpected

Dealing with a Code Analysis backlog?

The Visual Studio Code Analysis Team Blog — Sat, 05 May 2007 15:39:56 GMT

Nicole Calinoiu has started a (what I hope to be long) series on introducing Code Analysis (FxCop in

FxCop backlogs: Some rules for rule activation

I may have joined the wrong side — Sun, 29 Apr 2007 14:46:37 GMT

If you've decided to try to tackle an FxCop violation backlog , one of the first issues you're