Pour obtenir une clé
d'essai remplissez le formulaire ci-dessous
Demandez des tariffs
Nouvelle licence
Renouvellement de licence
--Sélectionnez la devise--
USD
EUR
RUB
* En cliquant sur ce bouton, vous acceptez notre politique de confidentialité

Free PVS-Studio license for Microsoft MVP specialists
To get the licence for your open-source project, please fill out this form
** En cliquant sur ce bouton, vous acceptez notre politique de confidentialité.

I am interested to try it on the platforms:
** En cliquant sur ce bouton, vous acceptez notre politique de confidentialité.

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#

22 Jul 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
Sorting in C#: OrderBy.OrderBy or OrderBy.ThenBy? What's more effective and why?

Date: 20 Sep 2022

Author: Sergey Vasiliev

Suppose we need to sort the collection by multiple keys. In C#, we can do this with the help of OrderBy().OrderBy() or OrderBy().ThenBy(). But what is the difference between these calls? To answer th…
ML.NET: can Microsoft's machine learning be trusted?

Date: 08 Sep 2022

Author: Andrey Moskalev

In 2018, Microsoft created ML.NET, a machine learning framework for .NET developers. Since then, the machine learning library has undergone significant changes and acquired new features to identify p…
The risks of using vulnerable dependencies in your project, and how SCA helps manage them

Date: 06 Sep 2022

Author: Nikita Lipilin

Most applications today use third-party libraries. If such a library contains a vulnerability, an app that uses this library may also be vulnerable. But how can you identify such problematic dependen…
Build to order? Checking MSBuild for the second time

Date: 01 Sep 2022

Author: Nikita Panevin

MSBuild is a popular open-source build platform created by Microsoft. Developers all over the world use MSBuild. In 2016, we checked it for the first time and found several suspicious places. Can we …
The Orchard Core threequel. Rechecking the project with PVS-Studio

Date: 25 Aoû 2022

Author: Aleksey Avdeev

In this article, we check the Orchard Core project with the help of the PVS-Studio static analyzer. We are going to find out if the platform code is as good as the sites created on its basis. May the…

Comments (0)

Next comments
Unicorn with delicious cookie
Nous utilisons des cookies pour améliorer votre expérience de navigation. En savoir plus
Accepter