Ok, I think I get it now :-). Basically, you want a fxcop task that can
be used as follows:
Which only checks the assemblies defined in the project file against the
rules defined in the project file.
Which checks the assemblies in the targets fileset agai
t file,
like so:
But I don't think we can combine this with any of the attributes
described above.
Do these changes make it more useful?
Best,
Arjen
> -Original Message-
> From: Gert Driesen [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 11, 2003 9:42 PM
> To: Ar
use a rules assembly, but turn off a couple specific rules from that
assembly. These are also stored in the project file.
-Original Message-
From: Arjen Poutsma [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 3:37 AM
To: Gert Driesen; [EMAIL PROTECTED]
Subject: RE: [nant-dev] F
ith any of the attributes
> described above.
I agree.
>
> Do these changes make it more useful?
I don't think so ... Really I urge you to use your task on some
"production" assemblies and I'm pretty sure you won't find one that
doesn't violate any
Hi Arjen,
Good to see someone finally took the time to implement these tasks, great
work
However, I'm not sure the FxCop task is very useful as you've implemented
it, but I could be wrong ofcourse ... I think we could actually start from
an existing FxCop project file as it doesn't make sense to
