Name

Key

Default value

Description

FxCop install directory

sonar.fxcop.installDirectory

C:/Program Files/Microsoft FxCop 10.0

Absolute path of the FxCop installation folder.

Assembly dependency directories

sonar.fxcop.assemblyDependencyDirectories

 

Comma-seperated list of path patterns to locate the directories where dependency assemblies can be found. These paths can be absolute or relative, the starting point being the folders where the csproj files are located. Also the special key "$(SolutionDir)" can be used to build a path relative to the root folder of the solution (i.e. where the sln file is located). Check out the note at the bottom of this page for more details.
E.g.: "$(SolutionDir)/**/libs" (and not "$(SolutionDir)/**/libs/*.dll")

Ignore generated code

sonar.fxcop.ignoreGeneratedCode

true

Suppress analysis results against generated code.

FxCop program timeout

sonar.fxcop.timeoutMinutes

10

Maximum number of minutes before the FxCop program will be stopped.

FxCop activation mode

sonar.fxcop.mode

 

Possible values : empty (means active), 'skip' and 'reuseReport'.

Name of the FxCop report files

sonar.fxcop.reports.path

 

Name of the FxCop report file used when reuse report mode is activated. This can be an absolute path, or a path relative to each project base directory.

Ant style patterns can be used. "*" means any file or any directory. "**" means any directory and subdirectory. For example "**/Foo*.dll" means any dll file prefixed by "Foo" anywhere in a project. IF you need to reference assembly files outside your solution folder, you can use absolute paths or "../". For example "$(SolutionDir)/../lib/**.*dll" can be used to specify all the dll files of a lib folder located at the same level as the root folder of your visual studio solution.

Each time you need to specify a path, or a pattern to locate files, use "/" instead of "\"