SONAR-14101 Update SonarScanner for MSBuild doc to reflect new 5.0 version. (#3309)

* Update SonarScanner for MSBuild doc to relfect new 5.0 version.

2 files changed, 129 insertions, 69 deletions

diff --git a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md
index 80bffe8caf3..5392ff77592 100644
--- a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md
+++ b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-azure-devops.md
@@ -18,6 +18,10 @@ The SonarScanner for Azure DevOps is compatible with:
 
 2. If you are self-hosting the build agents, make sure you have at least the minimum SonarQube-supported version of Java installed.
 
+[[info]]
+| The extension embeds its own version of the SonarScanner for .NET. 
+| Please check its [compatibility matrix](/analysis/scan/sonarscanner-for-msbuild/) to ensure you use the right version of SonarQube along with the version of the Scanner.
+
 ## Configure
 The first thing to do is to declare your SonarQube server as a service endpoint in your Azure DevOps project settings. 
 
diff --git a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-msbuild.md b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-msbuild.md
index b22edbccaab..46c866c6580 100644
--- a/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-msbuild.md
+++ b/server/sonar-docs/src/pages/analysis/scan/sonarscanner-for-msbuild.md
@@ -1,119 +1,163 @@
 ---
-title: SonarScanner for MSBuild
 url: /analysis/scan/sonarscanner-for-msbuild/
+title: SonarScanner for .NET
 ---
 
+<!-- sonarqube -->
 <update-center updatecenterkey="scannermsbuild"></update-center>
+<!-- /sonarqube -->
 
-The SonarScanner for MSBuild is the recommended way to launch an analysis for projects/solutions using MSBuild or dotnet command as a build tool. It is the result of a [collaboration between SonarSource and Microsoft](http://www.sonarqube.org/announcing-sonarqube-integration-with-msbuild-and-team-build/). 
+<!-- sonarcloud -->
+[[info]]
+| **Download SonarScanner for .NET 5.0.0** - [Issue Tracker](https://github.com/SonarSource/sonar-scanner-msbuild/issues) – [Source](https://github.com/SonarSource/sonar-scanner-msbuild)
+|
+| [Standalone executables](https://github.com/SonarSource/sonar-scanner-msbuild/releases/download/5.0.0.23533) |
+| [.NET Core Global Tool](https://www.nuget.org/packages/dotnet-sonarscanner)
+<!-- /sonarcloud -->
+
+[[info]]
+| Since version 5.0, the SonarScanner for MSBuild is now the SonarScanner for .NET. 
+| documentation is updated with that new name, artifacts and links will remain with the old name for now.
 
-SonarScanner for MSBuild is distributed as a standalone command line executable, as a extension for <!-- sonarcloud -->[Azure DevOps](/analysis/scan/sonarscanner-for-azure-devops/)<!-- /sonarcloud --><!-- sonarqube -->[Azure DevOps Server](/analysis/scan/sonarscanner-for-azure-devops/)<!-- /sonarqube -->, and as a plugin for [Jenkins](/analysis/scan/sonarscanner-for-jenkins/).
+The SonarScanner for .NET is the recommended way to launch an analysis for projects/solutions using MSBuild or dotnet command as a build tool. It is the result of a [collaboration between SonarSource and Microsoft](http://www.sonarqube.org/announcing-sonarqube-integration-with-msbuild-and-team-build/).
 
-It supports .Net Core multi-platform projects and it can be used on non-Windows platforms.
+SonarScanner for .NET is distributed as a standalone command line executable, as an extension for <!-- sonarcloud -->[Azure DevOps](/analysis/scan/sonarscanner-for-azure-devops/)<!-- /sonarcloud --><!-- sonarqube -->[Azure DevOps Server](/analysis/scan/sonarscanner-for-azure-devops/)<!-- /sonarqube -->, and as a plugin for [Jenkins](/analysis/scan/sonarscanner-for-jenkins/).
+
+It supports .Net Core on every platform (Windows, macOS, Linux).
 
 ## Prerequisites
+<!-- sonarqube -->
 * At least the minimal version of Java supported by your SonarQube server
+<!-- /sonarqube -->
+<!-- sonarcloud -->
+* Java 11 or greater
+<!-- /sonarcloud -->
 * The SDK corresponding to your build system:
-   *  [.NET Framework v4.6+](https://www.microsoft.com/fr-fr/download/details.aspx?id=53344) - either [Build Tools for Visual Studio 2015 Update 3](https://go.microsoft.com/fwlink/?LinkId=615458) or the [Build Tools for Visual Studio 2017](https://www.visualstudio.com/downloads/)
-   * .NET Core 2.0 - [.NET Core SDK 2.0](https://www.microsoft.com/net/learn/get-started/) (for .NET Core version of the scanner)
-   * .NET Core 2.1 - [NET Core SDK 2.1.3](https://www.microsoft.com/net/learn/get-started/) (for .NET Core version of the scanner or if you plan to use [.NET Core Global Tool](https://www.nuget.org/packages/dotnet-sonarscanner)
+   * [.NET Framework v4.6](https://www.microsoft.com/fr-fr/download/details.aspx?id=53344) - either [Build Tools for Visual Studio 2015 Update 3](https://go.microsoft.com/fwlink/?LinkId=615458) or the [Build Tools for Visual Studio 2017](https://www.visualstudio.com/downloads/)
+   * [.NET Core SDK 2.0 and above](https://dotnet.microsoft.com/download) (for .NET Core version of the scanner or if you plan to use [.NET Core Global Tool](https://www.nuget.org/packages/dotnet-sonarscanner)
+
+[[info]]
+| The flavor used to compile the Scanner for .NET (either .NET Framework, .NET Core or .NET) is independant of the .NET version the 
+| project you want to analyze has been built with. Concretly, you can analyze .NET Core code with the .NET Framework version of 
+| the Scanner. It's only relevant depending on your OS, and on the versions of .NET SDKs that are installed on your build machine.
 
+<!-- sonarqube -->
+### Compatibility
+
+Scanner Version|SonarQube
+---|---
+5.x| LTS 6.7+
+4.x| LTS 6.7+
+<!-- /sonarqube -->
 
 ## Installation
-### SonarScanner for MSBuild for .NET Framework or .NET Core
+
+### Standalone executable
+
 * Expand the downloaded file into the directory of your choice. We'll refer to it as `$install_directory` in the next steps.
-   * On Windows, you might need to unblock the ZIP file first (Right click on file > Properties > Unblock).
-   * On Linux/OSX you may need to set execute permissions on the files in `$install_directory/sonar-scanner-(version)/bin`.
-   
-* Uncomment, and update the global settings to point to your SonarQube server by editing `$install_directory/SonarQube.Analysis.xml`. Values set in this file will be applied to all analyses of all projects unless overwritten locally.  
+  * On Windows, you might need to unblock the ZIP file first (Right click on file > Properties > Unblock).
+  * On Linux/OSX you may need to set execute permissions on the files in `$install_directory/sonar-scanner-(version)/bin`.
+
+* Uncomment, and update the global settings to point to <!-- sonarqube -->your SonarQube server<!-- /sonarqube --><!-- sonarcloud -->SonarCloud<!-- /sonarcloud --> by editing `$install_directory/SonarQube.Analysis.xml`. Values set in this file will be applied to all analyses of all projects unless overwritten locally.  
 Consider setting file system permissions to restrict access to this file.:
-```
+
+```xml
 <SonarQubeAnalysisProperties  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.sonarsource.com/msbuild/integration/2015/1">
-  <Property Name="sonar.host.url">http://localhost:9000</Property>
+  <Property Name="sonar.host.url"><!-- sonarqube -->http://localhost:9000<!-- /sonarqube --><!-- sonarcloud -->https://sonarcloud.io<!-- /sonarcloud --></Property>
   <Property Name="sonar.login">[my-user-token]</Property>
 </SonarQubeAnalysisProperties>
 ```
 
 * Add `$install_directory` to your PATH environment variable.
 
-### Installation of the SonarScanner for MSBuild .NET Core Global Tool
-```
-dotnet tool install --global dotnet-sonarscanner --version 4.8.0
+### .NET Core Global Tool
+
+```bash
+dotnet tool install --global dotnet-sonarscanner --version x.x.x
 ```
-The _--version_ argument is optional. If it is omitted the latest version will be installed.
 
-### On Linux/OSX, if your SonarQube server is secured:
+The _--version_ argument is optional. If it is omitted the latest version will be installed. Full list of releases is available on the [NuGet page](https://www.nuget.org/packages/dotnet-sonarscanner)
+
+.NET Core Global Tool is available from .NET Core 2.1+
+
+<!-- sonarqube -->
+### On Linux/OSX, if your SonarQube server is secured
 
 1. Copy the server's CA certs to `/usr/local/share/ca-certificates`
 2. Run `sudo update-ca-certificates`
+<!-- /sonarqube -->
 
 ## Use
-There are two versions of the SonarScanner for MSBuild.
 
 [[info]]
-| Since version 4.7.0 of the Scanner, you can invoke it using arguments with both dash (-) or forward-slash (/) separators.
+| You can invoke the Scanner using arguments with both dash (-) or forward-slash (/) separators.
 | Example : SonarScanner.MSBuild.exe begin /k:"project-key" or SonarScanner.MSBuild.exe begin -k:"project-key" will work.
 
-The first version is based on the “classic” .NET Framework. To use it, execute the following commands from the root folder of your project:
+There are two versions of the SonarScanner for .NET.
+
+The first version is based on the "classic" .NET Framework. To use it, execute the following commands from the root folder of your project:
+
 ```
-SonarScanner.MSBuild.exe begin /k:"project-key" <!-- sonarcloud -->/d:sonar.organization="<organization>" /d:sonar.login="<token>" <!-- /sonarcloud -->
+SonarScanner.MSBuild.exe begin /k:"project-key" <!-- sonarcloud -->/o:"<organization>" /d:sonar.login="<token>" <!-- /sonarcloud -->
 MSBuild.exe <path to solution.sln> /t:Rebuild
 SonarScanner.MSBuild.exe end <!-- sonarcloud -->/d:sonar.login="<token>" <!-- /sonarcloud -->
 ```
-Note: On Mac OS or Linux, you can also use `mono <path to SonarScanner.MSBuild.exe>`.
 
+Note: On Mac OS or Linux, you can also use `mono <path to SonarScanner.MSBuild.exe>`.
 
 The second version is based on .NET Core which has a very similar usage:
-```
-dotnet <path to SonarScanner.MSBuild.dll> begin /k:"project-key" <!-- sonarcloud -->/d:sonar.organization="<organization>" /d:sonar.login="<token>" <!-- /sonarcloud -->
+
+```bash
+dotnet <path to SonarScanner.MSBuild.dll> begin /k:"project-key" <!-- sonarcloud -->/o:"<organization>" /d:sonar.login="<token>" <!-- /sonarcloud -->
 dotnet build <path to solution.sln>
 dotnet <path to SonarScanner.MSBuild.dll> end <!-- sonarcloud -->/d:sonar.login="<token>" <!-- /sonarcloud -->
 ```
+
 The .NET Core version can also be used as a .NET Core Global Tool.
 After installing the Scanner as a global tool as described above it can be invoked as follows:
-```
-dotnet sonarscanner begin /k:"project-key" <!-- sonarcloud -->/d:sonar.organization="<organization>" /d:sonar.login="<token>" <!-- /sonarcloud -->
+
+```bash
+dotnet tool install --global dotnet-sonarscanner
+dotnet sonarscanner begin /k:"project-key" <!-- sonarcloud -->/o:"<organization>" /d:sonar.login="<token>" <!-- /sonarcloud -->
 dotnet build <path to solution.sln>
 dotnet sonarscanner end <!-- sonarcloud -->/d:sonar.login="<token>" <!-- /sonarcloud -->
 ```
 
-Same as above, if you are targeting a SonarCloud project, will have to add both the organization and a login for authentication.
-
 Notes:
 
-* The .NET Core version of the scanner does not support TFS XAML builds. Apart from that, the two versions of scanner have the same capabilities and command line arguments.
-* Single .NET Core project files (csproj or vbproj) could be built and successfully analyzed only if a `<ProjectGuid>unique guid</ProjectGuid>` element is added in the csproj or vbproj XML. The `<ProjectGuid>` element is not required if you build a solution (sln) containing that project.
+* The .NET Core version of the scanner does not support TFS XAML builds and automatic finding/conversion of Code Coverage files. Apart from that, all versions of the Scanner have the same capabilities and command line arguments.
 
 ## Analysis steps
 ### Begin
-The begin step is executed when you add the `begin` command line argument. It hooks into the MSBuild pipeline, downloads SonarQube Quality Profiles and settings and prepares your project for the analysis.
+The begin step is executed when you add the `begin` command line argument. It hooks into the build pipeline, downloads {instance} quality profiles and settings and prepares your project for the analysis.
 
 Command Line Parameters:
 
 Parameter|Description
 ---|---
-`/k:<project-key>`|[required] Specifies the key of the analyzed project in SonarQube
-`/n:<project name>`|[optional] Specifies the name of the analyzed project in SonarQube. Adding this argument will overwrite the project name in SonarQube if it already exists.
+`/k:<project-key>`|[required] Specifies the key of the analyzed project in {instance}
+`/n:<project name>`|[optional] Specifies the name of the analyzed project in {instance}. Adding this argument will overwrite the project name in {instance} if it already exists.
 `/v:<version>`|[recommended] Specifies the version of your project.
-`/d:sonar.login=<username> or <token>`| [optional] Specifies the username or access token to authenticate with to SonarQube. If this argument is added to the begin step, it must also be added on the end step.
-`/d:sonar.password=<password>`|[optional] Specifies the password for the SonarQube username in the `sonar.login` argument. This argument is not needed if you use authentication token. If this argument is added to the begin step, it must also be added on the end step.
+<!-- sonarcloud --> `/o:<organization>`|[required] Specifies the name of the target organization in SonarCloud. <!-- /sonarcloud -->
+`/d:sonar.login=<username> or <token>`| [optional] Specifies the username or access token to authenticate with to {instance}. If this argument is added to the begin step, it must also be added on the end step.
+`/d:sonar.password=<password>`|[optional] Specifies the password for the {instance} username in the `sonar.login` argument. This argument is not needed if you use authentication token. If this argument is added to the begin step, it must also be added on the end step.
 `/d:sonar.verbose=true`|[optional] Sets the logging verbosity to detailed. Add this argument before sending logs for troubleshooting.
-`/d:<analysis-parameter>=<value>`|[optional] Specifies an additional SonarQube [analysis parameter](/analysis/analysis-parameters/), you can add this argument multiple times. 
+`/d:<analysis-parameter>=<value>`|[optional] Specifies an additional {instance} [analysis parameter](/analysis/analysis-parameters/), you can add this argument multiple times.
 
 For detailed information about all available parameters, see [Analysis Parameters](/analysis/analysis-parameters/).
 
 [[warning]]
-| The "begin" step will modify your build like this:
-| * the active `CodeAnalysisRuleSet` will be updated to match the SonarQube Quality Profile
+| ![](/images/exclamation.svg) The "begin" step will modify your build like this:
+| * the active `CodeAnalysisRuleSet` will be updated to match the {instance} quality profile
 | * `WarningsAsErrors` will be turned off
 |
-| If your build process cannot tolerate these changes we recommend creating a second build job for SonarQube analysis.
+| If your build process cannot tolerate these changes we recommend creating a second build job for {instance} analysis.
 
 ### Build
-Between the `begin` and `end` steps, you need to build your project, execute tests and generate code coverage data. This part is specific to your needs and it is not detailed here. This guide may help: [[Coverage & Test Data] Generate Reports for C#, VB.net](https://community.sonarsource.com/t/coverage-test-data-generate-reports-for-c-vb-net/9871).
+Between the `begin` and `end` steps, you need to build your project, execute tests and generate code coverage data. This part is specific to your needs and it is not detailed here.
 
 ### End
-The end step is executed when you add the "end" command line argument. It cleans the MSBuild hooks, collects the analysis data generated by the build, the test results, the code coverage and then uploads everything to SonarQube.
+The end step is executed when you add the "end" command line argument. It cleans the MSBuild/dotnet build hooks, collects the analysis data generated by the build, the test results, the code coverage and then uploads everything to {instance}
 
 There are only two additional arguments that are allowed for the end step:
 
@@ -123,14 +167,29 @@ Parameter|Description
 `/d:sonar.password=<password>`|[optional] This argument is required if it was added to the begin step and you are not using an authentication token.
 
 ### Known Limitations
+
 * MSBuild versions older than 14 are not supported.
-* Web Application projects are supported. Legacy Web Site projects are not. 
+* Web Application projects are supported. Legacy Web Site projects are not.
 * Projects targeting multiple frameworks and using preprocessor directives could have slightly inaccurate metrics (lines of code, complexity, etc.) because the metrics are calculated only from the first of the built targets.
 
+## Code Coverage
+
+In a Azure DevOps / TFS environment, test files are automatically retrieved following this search
+* Search for .trx files in any TestResults folder located under the $Build.SourcesDirectory path
+* If not found, then a fallback search is made against $Agent.TempDirectory
+
+Once trx files have been found, their `.coverage` counterpart are searched as well and the scanner tries to convert them to `.coveragexml` files that will be uploaded to {instance}.
+CodeCoverage.exe tool is used for that, and the scanner also needs to find a path to that tool, following this search path
+* Search for the presence of `VsTestToolsInstallerInstalledToolLocation` environment variable, set by the VsTestToolsPlatformInstaller task or by the user
+* If not found, search for either the presence of that tool in well-known installation path, or via the registry.
+
+As stated above, this will work only with the .NET 4.6 flavor of the Scanner.
 
 ## Excluding projects from analysis
+
 Some project types, such as [Microsoft Fakes](https://msdn.microsoft.com/en-us/library/hh549175.aspx), are automatically excluded from analysis. To manually exclude a different type of project from the analysis, place the following in its .xxproj file.
-```
+
+```xml
 <!-- in .csproj -->
 <PropertyGroup>
   <!-- Exclude the project from analysis -->
@@ -139,35 +198,25 @@ Some project types, such as [Microsoft Fakes](https://msdn.microsoft.com/en-us/l
 ```
 
 ## Advanced topics
+
 **Analyzing MSBuild 12 projects with MSBuild 14**  
-The Sonar Scanner for MSBuild requires your project to be built with MSBuild 14.0. We recommend installing Visual Studio 2015 update 3 or later on the analysis machine in order to benefit from the integration and features provided with the Visual Studio ecosystem (VSTest, MSTest unit tests, etc.).
+The Sonar Scanner for .NET requires your project to be built with MSBuild 14.0. We recommend installing Visual Studio 2015 update 3 or later on the analysis machine in order to benefit from the integration and features provided with the Visual Studio ecosystem (VSTest, MSTest unit tests, etc.).
 
 Projects targeting older versions of the .NET Framework can be built using MSBuild 14.0 by setting the "TargetFrameworkVersion" MSBuild property as documented by Microsoft:
 
 * [How to: Target a Version of the .NET Framework](https://msdn.microsoft.com/en-us/library/bb398202.aspx)
 * [MSBuild Target Framework and Target Platform](https://msdn.microsoft.com/en-us/library/hh264221.aspx)
 
-If you do not want to switch your production build to MSBuild 14.0, you can set up a separate build dedicated to the SonarQube analysis.
+If you do not want to switch your production build to MSBuild 14.0, you can set up a separate build dedicated to the {instance} analysis.
 
-**Detection of Test Projects**  
-SonarQube analyzes test projects differently from non-test projects, so it is important to correctly classify test projects.
+**Detection of test projects**
 
-By default, the SonarQube Scanner for MSBuild will detect as test project:
-
-. MSTest unit test projects, thanks to the presence of a well-known project type GUID in .csproj file of such projects.
-1. Projects with names ending in "Test" or "Tests". This behavior can be changed by providing the parameter `sonar.msbuild.testProjectPattern` to the begin step (regex follows .NET Regular Expression in a case-sensitive way with the default value `.*Tests?\.(cs|vb)proj$`). This regex is applied against the fullname of the `.csproj` or `.vbproj` which is why it's recommended to keep at the end of your custom regex `\.(cs|vb)proj$`.
-To manually classify a project as a test project, mark it with `<SonarQubeTestProject>true</SonarQubeTestProject>`:
-```
-<!-- in .csproj -->
-<PropertyGroup>
-  <!-- Mark the project as being a test project -->
-  <SonarQubeTestProject>true</SonarQubeTestProject>
-</PropertyGroup>
-```
+You can read a full description on that subject on our wiki [here](https://github.com/SonarSource/sonar-scanner-msbuild/wiki/Analysis-of-product-projects-vs.-test-projects).
 
 **Per-project analysis parameters**
 Some analysis parameters can be set for a single MSBuild project by adding them to its .csproj file.
-```
+
+```xml
 <!-- in .csproj -->
 <ItemGroup>
   <SonarQubeSetting Include="sonar.stylecop.projectFilePath">
@@ -177,26 +226,33 @@ Some analysis parameters can be set for a single MSBuild project by adding them
 ```
 
 **Concurrent Analyses on the Same Build Machine**  
-Concurrent analyses (i.e. parallel analysis of two solutions on the same build machine using a unique service account) are not supported by default by the Scanner for MSBuild. You can enable it as follows:
+Concurrent analyses (i.e. parallel analysis of two solutions on the same build machine using a unique service account) are not supported by default by the Scanner for .NET. You can enable it as follows:
 
-1. Locate the folder containing the Scanner for MSBuild
+1. Locate the folder containing the Scanner for .NET
 1. Go in the `Targets` folder and copy the folder `SonarQube.Integration.ImportBefore.targets`
 1. Paste it under your build tool global `ImportBefore` folder (if the folder doesn't exist, create it).
    * For MSBuild, the path is `<MSBUILD_INSTALL_DIR>\<Version>\Microsoft.Common.targets\ImportBefore` where <MSBUILD_INSTALL_DIR> is:
       * For v14, default path is: `C:\Program Files (x86)\MSBuild\14.0\Microsoft.Common.Targets\ImportBefore`
       * For v15, default path is: `C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Microsoft.Common.targets\ImportBefore` (for VS Community Edition)
-      * For v16, default path is: `C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Microsoft.Common.targets` (for VS Community Edition)
+      * For v16, default path is: `C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Microsoft.Common.targets` (for VS Enterprise Edition)
    * For dotnet, the path is `<DOTNET_SDK_INSTALL_DIR>\15.0\Microsoft.Common.targets\ImportBefore` where `<DOTNET_SDK_INSTALL_DIR>` can be found using the `dotnet --info` and looking for the Base Path property.
 
 The performance impact of this global installation for projects that aren't analyzed is negligible as this target is only a bootstrapper and will bail out nearly instantaneously when the `.sonarqube` folder is not found under the folder being built.
 
-**Using SonarScanner for MSBuild with a Proxy**  
-On build machines that connect to the Internet through a proxy server you might experience difficulties connecting to {instance}. To instruct the Java VM to use the system proxy settings, you need to set the following environment variable before running the SonarScanner for MSBuild:
-```
+**Using SonarScanner for .NET with a Proxy**  
+On build machines that connect to the Internet through a proxy server you might experience difficulties connecting to {instance}. To instruct the Java VM to use the system proxy settings, you need to set the following environment variable before running the SonarScanner for .NET:
+
+```bash
 SONAR_SCANNER_OPTS = "-Djava.net.useSystemProxies=true"
 ```
+
 To instruct the Java VM to use specific proxy settings or when there is no system-wide configuration use the following value:
-```
+
+```bash
 SONAR_SCANNER_OPTS = "-Dhttp.proxyHost=yourProxyHost -Dhttp.proxyPort=yourProxyPort"
 ```
+Where _yourProxyHost_ and _yourProxyPort_ are the hostname and the port of your proxy server. There are additional proxy settings for https, authentication and exclusions that could be passed to the Java VM. For more information see the following article: https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html.
+
+Since version 5.0 of the scanner, HTTP_PROXY, HTTPS_PROXY, ALL_PROXY and NO_PROXY will be automatically recognized and use to make call against {instance}. The Scanner for .NET makes HTTP calls, independant from the settings above concerning the Java VM, to fetch the Quality Profile and other useful settings for the "end" step.
+
 Where _yourProxyHost_ and _yourProxyPort_ are the hostname and the port of your proxy server. There are additional proxy settings for https, authentication and exclusions that could be passed to the Java VM. For more information see the following article: https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html