New FxCop 1.36 beta 2 released

Oct 23, 2007

I’ve always been a big fan of FxCop even though I’ve had my share of problems with some of the rules. The new beta version fixes all that. It works much better with ASP.NET which the previous versions didn’t do very well at all.

There are also some new rules to help you write better software. Especially two rules are popping up everywhere and those are the Specify StringComparison and Normalize strings to uppercase rules.

The Specify StringComparison rule helps you to do string searching in a better way by always specifying a StringComparison enum when you do string manipulation such as IndexOf and LastIndexOf etc.

The Normalize strings to uppercase rule makes sure you use ToUpper or ToUpperInvariant when you normalize strings. It is more efficient to upper case a string than to lower case it.

The design looks very much the same as the 1.35 version with some minor tweaks here and there. It also supports .NET 3.5. Overall, it’s a really good application and a much needed upgrade. You can download it here.

* $4.95/month ASP.NET Hosting with FREE SQL 2012 DB! – Click Here!

Running FxCop and the quirksUsing FxCop can bring pain if you don't know the quirks and what to ignoreInternet Explorer 7.0 beta 2For those of you who tried the beta 1 release, you would agree that a lot has happened since the...Use FxCop with ASP.NET 2.0The build process in ASP.NET 2.0 is very different than in ASP.NET 1.x, because it does not prod...

Comments (6) -

PWills

10/23/2007 6:29:32 PM #

>>It is more efficient to upper case a string than to lower case it.
Okay I give up... why?

Mads Kristensen

10/23/2007 6:34:38 PM #

I have no idea. It's been like that since .NET 1.0

Göran

10/23/2007 7:51:11 PM #

It might be revealed when we can see the source code!?

Göran

10/23/2007 9:06:36 PM #

This is what I ment: weblogs.asp.net/.../...et-framework-libraries.aspx

dani

10/24/2007 6:27:27 AM #

>>It is more efficient to upper case a string than to lower case it.

If you follow the link to MSDN it states clearly that the reason for this is primarily the small number of characters that can not make the round trip of being converted to lower and back again without loss.