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.
To get the licence for your open-source project, please fill out this form
* 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.
To get the licence for your open-source project, please fill out this form
* 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.
I am interested to try it on the platforms:
* 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.

>
>
Big PVS-Studio Update: Version 6.00 wit…

Big PVS-Studio Update: Version 6.00 with C# Support

Dec 22 2015

PVS-Studio 6.00 is now released! This is one of major updates for us. Hopefully, this information will be beneficial for our current and new users of the analyzer.

0362_PVS-Studio_6/image1.png

Static analysis for C#

We have added C# analysis support. We have already implemented more than 40 diagnostics for the C# module of the analyzer and this number will continue growing. Although the C# language is much more accurate than C++, we have noticed that some errors are not related to the programming language.

For example, it is so-called "Last line effect". We saw that very often an error gets to the last line of the code block that was written with Copy-Paste method. Unfortunately, it is impossible to protect yourself against such errors no matter how comfortable and well-thought out the language is. There are many more examples of such errors that are common for both C# and C++ languages.

How did we come up with the idea to make a C# analyzer? Currently (December, 2015) we have 235 diagnostics for C++. It turned out that only a part of them are related to coding in C++, the others are typical for C# as well. We have done the analysis of these diagnostics and chose those ones that could be relevant for C#. Besides that we researched the market of other C# analyzers and programming tools for working with the code. We saw that there is some room for our analyzer.

In order not to reinvent the wheel, we have taken Roslyn platform as the basis for our analyzer.

Support for Visual Studio 2005 and 2008 ended

For those who are already using PVS-Studio, the important news is that we are no longer supporting Visual Studio 2005 and Visual Studio 2008 starting from the 6.00 version of the analyzer. Thus PVS-Studio now supports all versions of Visual Studio from 2010 until 2015 (for the current moment – December, 2015). It is a compulsory measure for us. The more versions of Visual Studio we support, the harder it is to maintain them.

Firstly, according to the information we have very few users of PVS-Studio work with VS2005 or VS2008.

Secondly, we run tests for each version of Visual Studio we support. Consequently, the more versions need to be supported, the more tests will be located on the server.

Thirdly, it's not that easy to install and use the whole product line of Visual Studio 2005-2015 due to the conflicts of the versions.

That's why with the release of our 6.00 version we ceased supporting old versions of Visual Studio.

To make the transition process smoother, we will still provide the old 5.XX version of PVS-Studio during some period of time for those who continue working with VS2005 and 2008.

Further steps

We plan to continue developing this analyzer for our "traditional" languages - C and C++.

Besides that we will also work on the development of C# analyzer. In our "ToDo" list there are many more new diagnostics waiting to be implemented.

So now it's the right time to download the analyzer and run it on your code - whether it be written in C, C++ or C#.

Popular related articles
PVS-Studio for Java

Date: Jan 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…
PVS-Studio ROI

Date: Jan 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…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 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…
The way static analyzers fight against false positives, and why they do it

Date: Mar 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…
Free PVS-Studio for those who develops open source projects

Date: Dec 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…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 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…
The Evil within the Comparison Functions

Date: May 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…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
The Last Line Effect

Date: May 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: Jun 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…

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