Qodana for .NET

The Docker image for the Qodana for .NET linter is provided to support different usage scenarios:

Running the analysis on a regular basis as part of your continuous integration (CI-based execution)
Single-shot analysis (for example, performed locally).

If you are familiar with Rider code inspections and know what to expect from the static analysis outside the editor, you can skip the following section and continue from Using an existing profile.

If you are just starting in the field, we recommend proceeding with the default setup we provide. You will see the results of the most common checks performed on your code base. Later, you can adjust them to suit your needs better.

You can run the Qodana for .NET linter using two methods. Qodana CLI is the easiest method. If necessary, check the installation page to install Qodana CLI. Alternatively, you can use the Docker commands from the Docker image tab.

Quick start with the recommended profile

Run analysis locally

Pull the image from Docker Hub (only necessary to update to the latest version):
docker pull jetbrains/qodana-dotnet:2022.3-eap
Run the following command:
docker run --rm -it -p 8080:8080 \ -v <source-directory>/:/data/project/ \ -v <output-directory>/:/data/results/ \ jetbrains/qodana-dotnet:2022.3-eap --show-report
where source-directory and output-directory are full local paths to, respectively, the project source code directory and the analysis results directory.

This command will run the analysis on your source code and start the web server to provide a convenient view of the results. Open http://localhost:8080 in your browser to examine the found problems and performed checks. Here you can also reconfigure the analysis. See the User interface overview for details. When done, you can stop the web server by pressing Ctrl-C in the Docker console.

If you don't need the user interface and prefer to study raw data, use the following command:

                    docker run --rm -it \
                    -v <source-directory>/:/data/project/ \
                    -v <output-directory>/:/data/results/ \
                    jetbrains/qodana-dotnet:2022.3-eap
                

The output-directory will contain all the necessary results. You can further tune the command as described in the technical guide.

If you run the analysis several times in a row, make sure you've cleaned the results directory before using it in docker run again.

In the project root directory, run this command to inspect your code:

qodana scan -l jetbrains/qodana-dotnet:2022.3-eap --show-report

If you don't need the user interface and prefer to study raw data, use the following command:

                    qodana scan -l jetbrains/qodana-dotnet:2022.3-eap \
                    --results-dir <output-directory>
                

The output-directory specifies the directory where the SARIF-formatted report will be saved.

Run analysis in CI

Use the following command as a task in a generic Shell executor:

                    docker run --rm \
                    -v <source-directory>/:/data/project/ \
                    -v <output-directory>/:/data/results/ \
                    jetbrains/qodana-dotnet:2022.3-eap
                

where source-directory and output-directory are full paths to, respectively, the project source code directory and the analysis results directory.

Consider using the Quality gate feature to make the build fail when a certain number of problems is reached and the Baseline option to compare each new Qodana for .NET run to some initial run selected as a baseline. Running as non-root is also supported.

Run this command in the project root directory:

qodana scan -l jetbrains/qodana-dotnet:2022.3-eap --results-dir <output-directory>

This will save inspection results to the directory specified by output-directory.

You can also apply the Quality gate feature to make the build fail when a certain number of problems is reached by using the --fail-threshold option.

The Baseline feature compares each new Qodana for .NET run to some initial run using the --baseline and --baseline-include-absent options.

Using an existing profile

This section is intended for users familiar with configuring code analysis via Rider inspection profiles.

You can pass the reference to the existing profile by mapping the profile to /data/profile.xml inside the container:

                    docker run --rm -it -p 8080:8080 \
                    -v <source-directory>/:/data/project/ \
                    -v <output-directory>/:/data/results/ \
                    -v <inspection-profile.xml>:/data/profile.xml \
                    jetbrains/qodana-dotnet:2022.3-eap --show-report
                

You can pass the reference to the existing profile by mapping the profile inside the container:

                        qodana scan -l jetbrains/qodana-dotnet:2022.3-eap \
                        --results-dir <output-directory> \
                        --profile-path <path-to-profile> \
                        --show-report
                    

Configure via qodana.yaml

The qodana.yaml file will be automatically recognized and used for the analysis configuration, so that you don't need to pass any additional parameters.

The references to the inspection profiles will be resolved in a particular order. To learn about the format, see Configure profile.

Analyze specific solution or project

By default, Qodana tries to locate and employ a single solution file, or, if no solution file is present, it tries to find a project file. If your project contains multiple solution files, you need to specify the exact file name using the --property option. For example, to make Qodana always analyze the MySolution.sln solution file, you can use:

--property=qodana.net.solution=MySolution.sln

Alternatively, you can specify the solution file name in the qodana.yaml file using the solution option:

            dot-net:
                solution: MySolution.sln
        

If you project contains no solution files and multiple project files, you need to specify the exact file name of a project. For example, for the MyProject.csproj project file it can be:

--property=qodana.net.project=MyProject.csproj

Alternatively, you can specify the project file name in the qodana.yaml file using the project option:

            dot-net:
                project: MyProject.csproj
        

Inspect projects using private NuGet repositories

Qodana for .NET does not support authentication for private NuGet repositories using, for example, Windows Authentication. To overcome this limitation, you can place all required packages within the Qodana cache as shown below:

In the local filesystem, create the folder that will contain cache. For example, it can be C:/Temp/QodanaCache.
Run Qodana using the --cache-dir C:/Temp/QodanaCache option.
Copy all NuGet packages contained by default in the %userprofile%\.nuget\packages folder to C:/Temp/QodanaCache/nuget. If you have a custom package folder, copy packages from that folder instead of %userprofile%\.nuget\packages.
Run Qodana using the --cache-dir C:/Temp/QodanaCache once more.

Usage statistics

According to the JetBrains EAP user agreement, we can use third-party services to analyze the usage of our features to further improve the user experience. All data will be collected anonymously. You can disable the reporting of usage statistics by adjusting the options of the Docker command you use. Refer to the technical guide for details.

Last modified: 08 December 2022