The FxCop Action enables you to automate compliance testing of your .Net assemblies using FxCop.
The FxCop project file which houses all the rules and options to perform for the analysis.
The executable or dll's to perform the analysis on. If a directory is specified all exe and dll's in that directory have the analysis performed on them.
Specifies the location of the rules to load. If a directory is specified then all dll files are loaded and attempted to be used.
Specifies the location of the rules not to load. If a directory is specified then all dll's in that location are ignored unless included specifically.
The name of the analysis report which is generated by FxCop. The file will be overwritten if it exists.
The location of teh version of Mscorlib.dll that was used to build the target assembly.
Report XSL transformation file. This allows for transformation of the generated XML report on the fly.
Whether to capture the output of FxCop in the build log or not.
Whether to set the output from FxCop to its maximum level or not. If not selected the normal level is used.
Includes a summary report in the log when the analysis is completed. The report includes number of items found and how many were new.
Whether to save the result of the analysis to the supplied project file after the analysis is completed or not.
Whether to ignore generated code or not.
What culture to use for the spell checker.
Type and members to be included in the analysis. Leaving blank will mean all types and members in the configuration will be included.
Folders which should be checked for dependencies required the assemblies analysis.
Names for analysis reports to import into the current analysis.
See the FxCop homepage for more information, http://www.gotdotnet.com/team/fxcop/