Question

I m having problems getting the FxCop command line to work when I specify paths with spaces in them. Yes, I use the quotes properly.

M:uildIOServicesrc>"c:Program FilesMicrosoft FxCop 1.36FxCopCmd.exe" /c /f:".My LibraryinRelease" /r:"c:Program FilesMicrosoft FxCop 1.36Rules"
Microsoft (R) FxCop Command-Line Tool, Version 1.36 (9.0.30729.1)
Copyright (C) 2007 Microsoft Corporation.  All rights reserved.

Argument specified without a corresponding switch :  FilesMicrosoft .
Argument specified without a corresponding switch :  FxCop .
Argument specified without a corresponding switch :  1.36Rules" .

Type FxCopCmd.exe /? for help on command-line arguments.

FxCop complains about the path passed to the /r switch. I am quoting the path per the FxCop guidance. This also happens when I pass paths via the /d switch. Has anyone else had similar problems? It doesn t matter if I use cmd or PowerShell.

Answer 1

Remove the trailing slash on the rule switch fixes this issue (even in FX Cop 10.0)

Change:

/r:"c:Program FilesMicrosoft FxCop 1.36Rules"

To:

/r:"c:Program FilesMicrosoft FxCop 1.36Rules"

Answer 2

Have you tried accessing via old 8.3 filenames?

eg

"c:Progra~1Micros~1FxCopCmd.exe" /c /f:".MyLibr~1inRelease" /r:"c:Progra~1Micros~1Rules"

No guarantees that it will work as expected, but might be worth a go. :)

--edit-- I know it shouldn t need to use 8.3 names. It is a recent tool so should be more than capable of taking long names, but since it giving trouble this might be a starting point rather than a full solution. --end edit--

Answer 3

I had this problem when executing FXCop tasks from msbuild. It was creating the command line arguments with a similar pattern.

I got rid of this error by removing a flag: /d:"."

It looks suspiciously like your /f:".MyLibr~1inRelease" argument. Perhaps fxcop chokes on the "." and thinks everything after is no longer quoted? Try changing this to /f:"MyLibr~1inRelease" and see if that fixes it.

~Loren

友情链接