I'm using fxcopcmd.exe 1.35 as a post-build event and I want any FxCop violation to cause the build to fail. I know that the ability to treat FxCop warnings as build errors is limited to the FxCop that comes with VS 2005. I've been working around this limitation by checking for the existence of a Xml report file after each FxCop run. If the file exists, violations occurred. Otherwise, the code is clean. I'm just wondering if there's a simpler way to determine if violations occurred.
Getting FxCop violations to cause a build failure
Hot Topic
- Error while installing Team Foundation server
- Using stored procedures in web tests.
- Error 3200 ... /ReportServer/ReportService.asmx returned a non-zero value of xy
- Do Not Catch General Exception Types
- Using context variables from one webtest into another webtest
- Excel workItems menu doesn't appear
- Multiple users for the same task
- Any document about extensibility of profile, coverage and so on?
- Using VS2005 (beta 2) with custom rules
- mstest with custom test type and metadata(vsmdi) file?
VS Team System
- HTTPS or VPN to access TFS
- Workspaces meant only for filtering?
- Bug in tf merges?
- Reading Content of VSTF File without downloading to local machine
- A branch has been deleted but tf get still gets files in the branch
- Can not build team project
- Error with reports in TFS Beta 3 Refresh
- Is there a GUI for some common source control queries?
- Team Foundation Server installation error
- Stopping a Team Build
Getting FxCop violations to cause a build failure
MmmBeer
Hi Craig,
Checking for the existence of an output report is the recommended way to go. Alternatively you can add an extra step with a small app/task that parses the output log for existence of violations of certain rules. The Xml subdirectory of FxCop contains an xsd for the FxCopReport format.
Regards,
Jeffrey