FxCop Delta

NEW POST: FxCop Delta

Sowbhagya — Tue, 22 Apr 2008 07:03:05 GMT

Can Anyone tell me in detail what FxCop Delta does.And how to make it work on VS 2008

CREATED FEATURE: Add full logging/tracing to the code

elio — Tue, 26 Feb 2008 14:29:50 GMT

When running the code on some clients there are problems.
We should add full tracing to the code.
I suggest using a policy injection (Enterprise Library/ PostSharp) to log to a file:
- All Entering & Exits of methods
- All Exceptions thrown, weather caught or not.
- Input & output, ie: Number of changeset, time of operation, outcome of rule (passed/failed, with how many errors)

The trace should be activated on demand by editing the registry or the config file.

CREATED ISSUE: Fxcop rule does not run on some installations

elio — Tue, 26 Feb 2008 14:24:29 GMT

When installing on a Visual Studio 2005,
On some clients the Symbols check is running, but the fxcop doesn't do anything.
during checkin it completes the check instantly (not doing anything), weather the code should pass or not.
There is no logging / tracing available yet, so it's hard to trace the code.

Source code checked in

rauchy — Tue, 26 Feb 2008 12:59:35 GMT

Initial dump.

UPDATED WIKI: Home

rauchy — Tue, 26 Feb 2008 12:47:35 GMT

Project Description
A custom check-in policy for Visual Studio Team System that runs FxCop rules before performing a check-in. FxCop Delta differs from the normal static analysis policy by running FxCop only on the code that changed since checking out, thus eliminating tens or hundreds of static analysis errors every time you check-in.