Message-ID: <813933438.8967.1416714663289.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8966_1146301525.1416714663288" ------=_Part_8966_1146301525.1416714663288 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The plugin provides smooth integration between Visual Studio and SonarQu= be. It reads solution (*.sln) and project (*.csproj, *.vbproj) files to aut= omatically configure many of the required analysis parameters.
This plugin does not require Visual Studio to be instal= led.
Once installed, this plugin is enabled globally or on a project-by-=
project basis via the project settings: Configuration > Set=
tings > Visual Studio Bootstrapper > Enable the analysis bootstrappin=
g or in your properties file by setting
Once enabled, it is invoked in the analysis of projects containing a .sl= n file. Note that a sonar-project.properties file is still required to specif= y the basic project configuration.
By default, assemblies will be sought in the relevant binary directories=
of each project. If assemblies exist for multiple build configurations, th=
e most recent ones will be used. To specify an alternate location for the s=
olution binaries, set Configuration > Settings > Visual Studi=
o Bootstrapper > Assemblies output paths, or set the
sonar.visualstudio.outputPaths in the sonar-project.properties file=
Test projects can be imported as unit test code (which is not analyzed b=
y coding rules) using the regular expression property "
You can pass per-project settings by prefixing the properties by the pro=
ject name, for example setting the "
sPaths" will set the Visual Studio Test Execution Results repor=
t to be used only by the project named "Tests".
FxCop requires the assemblies of every project to be built. In Visual St=
udio, you can configure some projects not to be built in some particular bu=
ild configuration. In such situations, the FxCop analysis will fail complai=
ning that the assemblies are missing. Simply set the "
alstudio.skipIfNotBuilt" property to true to automatically skip=
those projects and prevent the failure of the overall SonarQube analysis.<=
You can fully exclude projects from the analysis by setting the regular =
expression property "
sonar.visualstudio.skippedProjectPattern". For example, setting the property to "
.*debug.*" will skip every project whose name contains "debug".