To get a trial key
fill out the form below
Team License (standard version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
>
Getting Started with the PVS-Studio Sta…

Getting Started with the PVS-Studio Static Analyzer for Visual C#

July 22, 2019

PVS-Studio is a tool for detecting software bugs and potential vulnerabilities in the source code of software written in C, C++, C#, and Java. The analyzer runs on Windows, Linux, and macOS.

0641_PVS_Studio_Visual_CSharp/image1.png

To be able to work with Visual C#, the analyzer integrates into Visual Studio as a plugin. This allows you to use Visual Studio's interface to customize the analyzer's settings, quickly and easily check individual files, projects, and solutions, and to handle PVS-Studio reports as well.

The hardware requirements for this mode are the same as those of the Visual Studio IDE that you work in.

The PVS-Studio installer can be downloaded here. The download page also offers a number of different use modes, including trial mode. See the purchase guide for licensing details.

To install the plugin, run the PVS-Studio installer and tick the desired Visual Studio versions:

0641_PVS_Studio_Visual_CSharp/image2.png

The analyzer is ready to run immediately after installation.

Run Visual Studio, open your project, click the "Extensions" main menu and then the "PVS-Studio" submenu (in Visual Studio versions earlier than 2019, the "PVS-Studio" menu is placed right on the menu bar).

A drop-down menu will appear with all the plugin's features available for use.

To check the entire solution, click the "Check" submenu and then "Solution". The analyzer will start preparing for the check:

0641_PVS_Studio_Visual_CSharp/image3.png

After that, the analysis process starts:

0641_PVS_Studio_Visual_CSharp/image4.png

Even before the check is over, warnings will start to appear in the report (PVS-Studio window) as the analyzer runs on, so you can start examining the respective code fragments right away. Double-clicking on a warning will take you to the corresponding code snippet in the Visual Studio editor, with suspicious lines highlighted:

0641_PVS_Studio_Visual_CSharp/image5.png

Clicking a diagnostic number link (for example, V3095) in the PVS-Studio window will take you to the documentation on that diagnostic, where you can learn the details about it and ways to fix bugs it detects.

You can save analysis results to study them later. To do that, open the "Extensions" menu, then "PVS-Studio" -> "Open/Save" -> "Save Analysis Report" (in Visual Studio versions earlier than 2019, the "PVS-Studio" menu is placed right on the menu bar).

We keep working to make our C# analyzer better. As one of the latest innovations, we added support of Nullable Reference types for the C# 8.0 standard.

To learn more about the features of the PVS-Studio Windows plugin, see the article "Getting acquainted with the PVS-Studio static code analyzer on Windows".

You can also use command-line utilities to check Visual C# projects and solutions. This use mode is extensively covered in the article "Analyzing Visual Studio projects from the command line".

Finally, the article "PVS-Studio and Continuous Integration" explains how PVS-Studio can be used in expert inspection.

Try PVS-Studio - get rid of bugs!

Popular related articles
The way static analyzers fight against false positives, and why they do it

Date: 03.20.2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
The Last Line Effect

Date: 05.31.2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
Static analysis as part of the development process in Unreal Engine

Date: 06.27.2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
PVS-Studio ROI

Date: 01.30.2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
The Evil within the Comparison Functions

Date: 05.19.2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
PVS-Studio for Java

Date: 01.17.2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
Appreciate Static Code Analysis!

Date: 10.16.2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: 11.21.2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
Free PVS-Studio for those who develops open source projects

Date: 12.22.2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: 07.31.2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept