Start FreeLogin

.NET project

Use these instructions to set up your build pipeline in Azure DevOps when analyzing .NET projects in SonarQube Cloud.

Before starting, read Azure Pipelines integration overview.

Once you have created your project in SonarQube Cloud, set up the project integration with your DevOps platform (see the DevOps platform integration pages) and with Azure pipelines (see the Setting up project integration page), you can add the SonarQube Cloud analysis to your Azure build pipeline.

To create your Azure build pipeline, you can use either YAML or the Azure Classic interface.

  • The use of the Classic interface is not always possible (e.g. if your code is stored on GitHub).

  • If you use YAML, Sonar can provide you with YAML templates or code examples.

If you need to use a specific scanner version, see Using various features.

Make sure to enable the pull request and branch analysis in your pipeline. See the Setting up project integration page.

About the analysis parameter setup

Analysis parameters can be set at different levels. When creating your pipeline, you will have to enter the project key and you may also enter the project version and name. For more information about these task inputs, see the Task inputs specific to the .NET mode article. You may define additional parameters in this task. In that case, these parameters have precedence over parameters defined at the project or global level.

Using YAML

Add the following SonarQube tasks to your YAML pipeline:

  1. Before your build task, add a Prepare Analysis Configuration task.

  2. After your build task, add a Run Code Analysis task.

  3. After the Run Code Analysis task, add a Publish Quality Gate Result task.

See the YAML file example below. See also our YAML pipeline templates. For information about the SonarQube task inputs, see the List of SonarQube tasks page.

Make sure the SonarQube task version used in your YAML file is the correct one. For example, in SonarCloudPrepare@3, @3 should correspond to the version of the Azure DevOps Extension you’re using.

YAML file example
trigger:
- master # or the name of your main branch
- feature/*

steps:
 # Checkout the repository 
- checkout: self

 # Disable shallow fetch
  fetchDepth: 0

# Prepare Analysis Configuration task
- task: SonarCloudPrepare@3
  inputs:
    SonarCloud: '<YourSonarQubeServiceEndpoint>'
    organization: '<YourOrganizationName>'
    scannerMode: 'dotnet'
    projectKey: '<YourProjectKey>'

# Dotnet build task
- task: DotNetCoreCLI@2
  displayName: 'dotnet build'

# Run Code Analysis task
- task: SonarCloudAnalyze@3

# Publish Quality Gate Result task
- task: SonarCloudPublish@3
  inputs:
    pollingTimeoutSec: '300'

Using the Classic interface

To add the analysis to your classic build pipeline:

  1. In Azure DevOps Classic interface editor, create or update your build pipeline.

  2. Add a Prepare Analysis Configuration task before your build task:

    • In SonarQube Cloud Service Endpoint, select the SonarQube Cloud service connection you created in Adding the SonarQube service connection to your AzDO project. See the Azure DevOps page for more details.

    • Under Choose a way to run the analysis, select Integrate with MSBuild.

    • In the Project key field, enter your project key.

    • Optionally, enter the project name and version.

  3. Add a new Run Code Analysis task after your build task.

  4. Add a new Publish quality gate Result on your build pipeline summary.

  5. Ensure that the pipeline runs automatically for all the branches you want:

    • Under the Triggers tab of your pipeline, select Enable continuous integration and select all the branches for which you want SonarQube Cloud analysis to run automatically.

  6. Save your pipeline.

.Net guides on the Sonar Community forum

We’ve prepared some guides on the Community Forum to help you with your .NET project.

.NET Configuration

.NET and Code coverage

Related pages

PreviousC family projectNextGradle or Maven project

Last updated

Was this helpful?