FxCop

  • Thread starter Thread starter Paul Buckley
  • Start date Start date
P

Paul Buckley

I've recently been enforcing coding standards in my project using FxCop.
I've noticed that some of the standard rules are not applied to non-public
members (i.e. internal classes and private methods). Am I the only person
that thinks it's a good idea to enforce standards on all classes and
methods, whether they are public or not?

Paul.
 
Hi Paul,

No need to enforce on internals and privates since they won't be used by
external assemblies - this is the point of FxCop.
 
I think enforcing these rules on public members is very important if you
want to share your compiled component with other people. On the other hand,
applying the rules also on the internal members (e.g. private) can be very
important if you share to code with for example other colleagues. So my
opinion: yes these rules should apply on all members, also the internal
ones. Although I can understand the goals of FXCop.
 
Paul,
I would agree with you. I've been thinking about using FxCop, but I will not
do so if it doesn't allow me to enforce coding standards on all code. Anyone
know of another tool that would not have this "feature"?
Regards,
Mountain
 
Thanks, but it's too expensive for me, and it doesn't mention C# (only C++)

for unit testing, I'm looking into HarnessIT
 
Yes, it must be expensive, but I think it works with C# (I doubt that it
works with C++, though; I think that C++ Test does, not .Test). Anyway, it
(I mean, the pricing) seems to be more for corporate customers with deeper
pockets. A nice tool, though. I should check out HarnessIT, haven't tried
this one.

Alek
 
Back
Top