From: michaelbirnstiehl <michael.birnstiehl@sonarsource.com>
Date: Tue, 1 Dec 2020 21:25:36 +0000 (-0600)
Subject: DOCS update links to SonarScanner for MSBuild
X-Git-Tag: 8.6.0.39681~29
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=3472391d3f025d31bc0c3167f8818861a60c46ea;p=sonarqube.git

DOCS update links to SonarScanner for MSBuild
---

diff --git a/server/sonar-docs/src/pages/analysis/overview.md b/server/sonar-docs/src/pages/analysis/overview.md
index a2f048d52ac..613a7c99f40 100644
--- a/server/sonar-docs/src/pages/analysis/overview.md
+++ b/server/sonar-docs/src/pages/analysis/overview.md
@@ -6,7 +6,7 @@ url: /analysis/overview/
 Once the SonarQube platform has been installed, you're ready to install a scanner and begin creating projects. To do that, you must install and configure the scanner that is most appropriate for your needs. Do you build with:
 
 * Gradle - [SonarScanner for Gradle](/analysis/scan/sonarscanner-for-gradle/)
-* MSBuild - [SonarScanner for MSBuild](/analysis/scan/sonarscanner-for-msbuild/)
+* .NET - [SonarScanner for .NET](/analysis/scan/sonarscanner-for-msbuild/)
 * Maven - use the [SonarScanner for Maven](/analysis/scan/sonarscanner-for-maven/)
 * Jenkins - [SonarScanner for Jenkins](/analysis/scan/sonarscanner-for-jenkins/)
 * Azure DevOps - [SonarQube Extension for Azure DevOps](/analysis/scan/sonarscanner-for-azure-devops/)
diff --git a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-jenkins.md b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-jenkins.md
index ca373f9af99..7ee272fd082 100644
--- a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-jenkins.md
+++ b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-jenkins.md
@@ -12,7 +12,7 @@ Then you can trigger SonarQube analysis from Jenkins using standard Jenkins Buil
 * [SonarScanner](/analysis/scan/sonarscanner/)
 * [SonarScanner for Maven](/analysis/scan/sonarscanner-for-maven/)
 * [SonarScanner for Gradle](/analysis/scan/sonarscanner-for-gradle/)
-* [SonarScanner for MSBuild](/analysis/scan/sonarscanner-for-msbuild/)
+* [SonarScanner for .NET](/analysis/scan/sonarscanner-for-msbuild/)
 
 Once the job is complete, the plugin will detect that a SonarQube analysis was made during the build and display a badge and a widget on the job page with a link to the SonarQube dashboard as well as quality gate status.
 
@@ -25,7 +25,7 @@ Once the job is complete, the plugin will detect that a SonarQube analysis was m
 
 ## Analyzing a .NET solution
 **Global Configuration**  
-This step is mandatory if you want to trigger any of your analyses with the SonarScanner for MSBuild. You can define as many scanner instances as you wish. Then for each Jenkins job, you will be able to choose which launcher to use to run the SonarQube analysis.
+This step is mandatory if you want to trigger any of your analyses with the SonarScanner for .NET. You can define as many scanner instances as you wish. Then for each Jenkins job, you will be able to choose which launcher to use to run the SonarQube analysis.
 1. Log into Jenkins as an administrator and go to **Manage Jenkins > Global Tool Configuration**
 1. Click on **Add SonarScanner for MSBuild**
 1. Add an installation of the latest available version. Check **Install automatically** to have the SonarScanner for MSBuild automatically provisioned on your Jenkins executors
@@ -132,7 +132,7 @@ node {
   }
 }
 ```
-SonarScanner for MSBuild:
+SonarScanner for .NET:
 ```
 node {
   stage('SCM') {
diff --git a/server/sonar-docs/src/pages/analysis/scan/sonarscanner.md b/server/sonar-docs/src/pages/analysis/scan/sonarscanner.md
index d60e96bc91b..7c62ea16dd9 100644
--- a/server/sonar-docs/src/pages/analysis/scan/sonarscanner.md
+++ b/server/sonar-docs/src/pages/analysis/scan/sonarscanner.md
@@ -178,5 +178,5 @@ set SONAR_SCANNER_OPTS=-Xmx512m
 Upgrade the version of Java being used for analysis or use one of the native package (that embed its own Java runtime).
 
 **Property missing: `sonar.cs.analyzer.projectOutPaths'. No protobuf files will be loaded for this project.**  
-Scanner CLI is not able to analyze .NET projects. Please, use the Scanner for MSBuild. If you are running Scanner for MSBuild, ensure that you are not hitting a known limitation.
+Scanner CLI is not able to analyze .NET projects. Please, use the SonarScanner for .NET. If you are running the SonarScanner for .NET, ensure that you are not hitting a known limitation.