FxCop does anyone use it ?

  • Thread starter Thread starter Søren Reinke
  • Start date Start date
S

Søren Reinke

Hi there

I have played around a bit with FxCop.

Does anyone use it ? Some of the warning/errors it gives are okay, when
there are implementation errors, but i think it is annoying it keeps
complaining about how i case my variables and more.

What is your oppinion about the program ?
 
Hey soren,
lol, yeah I know what you mean about FxCop complaining about all the
little things that sometimes you may not even consider important at all. I
used it a few times and found that it made pretty good 'suggestions'.
Remember that these 'warnings' etc are simply recomendations / suggestions
that you can use to make you code better in some way. Also remember that
these are simply configurable rules and you can exclude your project from
being tested against them, you can also create and add you own rules, so all
in all I think that its a great tool. I actually shoudl use it some more.

(that my own humble opinion)
Cordell Lawrence
Teleios Systems Ltd.
 
Cordell Lawrence said:
Hey soren,
lol, yeah I know what you mean about FxCop complaining about all the
little things that sometimes you may not even consider important at all. I
used it a few times and found that it made pretty good 'suggestions'.
Remember that these 'warnings' etc are simply recomendations / suggestions
that you can use to make you code better in some way. Also remember that
these are simply configurable rules and you can exclude your project from
being tested against them, you can also create and add you own rules, so
all
in all I think that its a great tool. I actually shoudl use it some more.
Click to expand...

Hi Cordell

Thanks for the info, i have reconfigured the tool to stop complaining about
naming of variable, that did help a lot.

I agree with you that it gives some good tips about stuff like things you
need to dispose, remember to use CultureInfo and more like that :)

I think it is a bit funny it does complain about some of the stuff Visual
Studio makes when creating a component og a Dataset :-)
 
We use it, and we think it is great. However, the guidelines have evolved at
the same time we developed our framework, so we find "new" warnings on old
code often when we upgrade FxCop. Internal MS code breaks many guidelines.

Despite these problems, it is a great tool. It has found many small
usability, performance, and localization problems in our API and our code in
general. We could never have complied to so many guidelines without FxCop.
You will notice that new warnings come out in bold, so they are easier to
track -- and generally more important.

Regards,
Frank Hileman

check out VG.net: http://www.vgdotnet.com
Animated vector graphics system
Integrated Visual Studio .NET graphics editor
 
I think it is a bit funny it does complain about some of the stuff Visual
Studio makes when creating a component og a Dataset :-)
Click to expand...

Try running FxCop on Microsoft's own Framework DLLs for a laugh.
System.Web.dll v1.1 shows a whopping 2,720 issues! Still, the tool is
somewhat useful once you turn off about half of the messages...
 
Frank Hileman said:
We use it, and we think it is great. However, the guidelines have evolved
at the same time we developed our framework, so we find "new" warnings on
old code often when we upgrade FxCop. Internal MS code breaks many
guidelines.

Despite these problems, it is a great tool. It has found many small
usability, performance, and localization problems in our API and our code
in general. We could never have complied to so many guidelines without
FxCop. You will notice that new warnings come out in bold, so they are
easier to track -- and generally more important.
Click to expand...

Thanks for the tips :) I'll sure use the program.
 
Soren,

It has sense and nonsense, you have to finetune the tool I guess:

For instance it founds out if you catch Exception if you could have
catched more specific Exceptions.

But also it tells us that we cant use three Capitals behind each other
for namespace names while our company is known by those capitals..

Rick


We use it, and we think it is great. However, the guidelines have evolved at
the same time we developed our framework, so we find "new" warnings on old
code often when we upgrade FxCop. Internal MS code breaks many guidelines.

Despite these problems, it is a great tool. It has found many small
usability, performance, and localization problems in our API and our code in
general. We could never have complied to so many guidelines without FxCop.
You will notice that new warnings come out in bold, so they are easier to
track -- and generally more important.

Regards,
Frank Hileman

check out VG.net: http://www.vgdotnet.com
Animated vector graphics system
Integrated Visual Studio .NET graphics editor
Click to expand...
 
There is a custom dictionary you can modify. Look in the docs.

Regards,
Frank Hileman

check out VG.net: http://www.vgdotnet.com
Animated vector graphics system
Integrated Visual Studio .NET graphics editor
 
Back
Top