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
of these rules are just
guidelines that could and in some cases actually should be ignored.
Gert
Best,
Arjen
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 9:42 PM
To: Arjen Poutsma; [EMAIL PROTECTED]
Subject: Re: [nant-dev] FxCop
, 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] FxCop RegSvcs Tasks
Driesen [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 9:42 PM
To: Arjen Poutsma; [EMAIL PROTECTED]
Subject: Re: [nant-dev] FxCop RegSvcs Tasks
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
Ok, I think I get it now :-). Basically, you want a fxcop task that can
be used as follows:
fxcop report=myreport.fxcop/
Which only checks the assemblies defined in the project file against the
rules defined in the project file.
fxcop report=myreport.fxcop
targets basedir=bin
