FxCop Runner Bugs

Bug #1: Search referenced assemblies in directories

The "Search referenced assemblies in directories" appears to do nothing. What it SHOULD do is take each directory specified in the textbox and append it to the fxcopcmd command as a /d: switch. To replicate:

  1. Create a new build configuration with a FxCop Runner.
  2. In the "Search referenced assemblies in directories" textbox, enter the word "References".
  3. Save and run the build configuration.
  4. Check the build's Build Log -> All Messages page.


What you SHOULD see is something like:

Start process:"c:\Program Files (x86)\Microsoft FxCop 1.36\FxCopCmd.exe" /forceoutput /gac /f:Binaries\*.dll /d:References /out:05A1B22A-DE6E-49ae-AA30-DC52A074EF22\fxcop-result.xml

... but instead, there will be no /d: parameter.

Bug #2: Additional FxCopCmd options

The "Additional FxCopCmd options" textbox incorrectly handles doublequotes. To replicate:

In the FxCop runner configuration, enter the following into the "Additional FxCopCmd options" textbox: /d:References1 /d:References2
Save and run the build configuration.
Verify (via the Build Log) that fxcopcmd was executed with the correct arguments.
In the FxCop runner configuration, change /d:References1 to /d:"My References".
Save and run the build configuration.
Check the Build Log again.

This time you will see that instead of the arguments looking like

/d:"My References" /d:References2

... you will see:

"/d:"My References"" /d:References2

(Note the extraneous doublequotes around the first parameter.)

5 comments
Comment actions Permalink

Thank you for your feedback.

I filled two issues: http://www.jetbrains.net/tracker/issue2/TW-8427 and http://www.jetbrains.net/tracker/issue2/TW-8426
I'll post a patch here as soon as I fix it.

0
Comment actions Permalink

TW-8426 was fixed and fix will be available in 4.5.3 (soon). As for TW-8427 you can quote an entire string ("/d:My Reference")

0
Comment actions Permalink

Thank you Leonid. WIth 8426 fixed, I won't have a need for 8427 for this scenario anyway as was just trying to find a workaround for 8426. It was just a perfect storm of bugs that happened to make the FxCop runner entirely unusable for my purposes. Looking forward to 4.5.3!

0
Comment actions Permalink

Hello Troy,

  TeamCity 4.5.3 is out, so please try it, 8426 must be fixed.

  Hope this helps,
  KIR

0
Comment actions Permalink

It is working fine now. Thanks for the quick response!

0

Please sign in to leave a comment.