Create a Sonar file for your solution
Here is the simplest "sonar-project.properties" file that you can write to be able to run a Sonar analysis for your project:
"sonar-project.properties" file for the Simple Java Runner
The "sonar.projectKey" parameter will create a unique identifier in Sonar for your C# solution.
C# plugins options
Every C# plugin defines its own options that can be overriden, may it be through the Sonar configuration file that you've just created or through Sonar "System Settings" web page. You will find below the pages that describe each C# plugin options:
Paths and file patterns
Each time you need to define the location of a file or a set of files, use '/' instead of '\' (even if that looks weird on a windows box)
If you need to specify a path, this path may be absolute or relative. Relative paths may start from the location of the sln file or the csproj files, depending of the property specified. Relative paths may use "../" to climb in the folder hierarchy.
When several files need to be specified, for example for properties such as "sonar.dotnet.assemblies", "Ant style" wildcard patterns can be used. "*" means any file or any directory. "**" means any directory and subdirectory :
Above pattern will select any dll files prefixed by "Foo" anywhere in a project.
You can combine an absolute path prefix with wildcards :
This will select any dll files in any subfolder of the "lib" folder of the drive "T:".
If you need to reference assembly files outside your solution folder, you can use absolute paths or "../". For example :
Above pattern 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.