changes.
| To publish Fxcop reports, you need: |
| |
| # Generate Fxcop reports by using [FxcopCmd|http://msdn.microsoft.com/en-us/library/bb429449(VS.80).aspx] or [NAnt fxcop task|http://nantcontrib.sourceforge.net/release/latest/help/tasks/fxcop.html] or any other tools. |
| # Add a Publish Fxcop Reports step in your configuration steps. |
| |
| *Note:* The Fxcop version should be 1.35+. |
| |
| After doing this, QuickBuild will generate the Fxcop reports automatically. |
| |
| *NOTE* QuickBuild only parses the XML reports. |
| |
| h2. Generate Fxcop XML Reports |
| |
| We use NAnt fxcop task as an example for how to generate Fxcop XML reports: |
| |
| {code:xml} |
| <fxcop failonerror="false" projectFile="${build.dir}\Sample.fxcop"> |
| <targets> |
| <include name="${build.dir}\bin\*.dll" /> |
| </targets> |
| <rules> |
| <include name="${build.dir}\rules\*.dll" /> |
| </rules> |
| </fxcop> |
| {code} |
| |
| h2. Publish Fxcop Reports |
| | Just like all other [build reports|Publish Build Reports], you add Fxcop report by adding a publish step in a configuration. When you add publish Fxcop Report step, the following screen will be displayed: |
| !Screenshots^report_publish_step.png! |
| |
| In Report Files/Patterns field, QuickBuild uses Ant style file patterns to collect the reports, and the directory you specified is *relative* to the [workspace|Configuration Workspace] directory. |
| |
| If you have several report sets, you can add several publish Fxcop steps with different report set names. |
| | Add _*Publish Fxcop Report*_ step to your build workflow. If you have several report sets, you can add several steps with different report set names. Reference [this page|Publish Build Reports] for more details. |