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

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

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

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

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.

How to disable IntelliSence in Visual S…

How to disable IntelliSence in Visual Studio 2010?

May 13 2010

The question how to disable IntelliSence in Visual Studio 2005 and Visual Studio 2008 was very popular among programmers some time ago. There was even a huge topic on the MSDN forum where this issue was discussed. Deleting the file feacp.dll appeared to be the right solution.

The developers took this experience into account when working on Visual Studio 2010 and brought significant modifications both into the IntelliSence mechanism itself and means of disabling it.

In Visual Studio 2010, you may disable IntelliSence through the settings page of "Tools|Options" menu: Text Editor->C/C++->Advanced.

Why do we, PVS-Studio analyzer developers, discuss the question of disabling IntelliSence in Visual Studio 2010? Unfortunately, the new IntelliSence "spoils our life a bit". Since this mechanism is new and seems to be not fixed completely, it involves some problems. Sometimes (we did not manage to find out in what conditions), IntelliSence in Visual Studio 2010 adds its messages into Error List at the same time when our analyzer PVS-Studio generates its own messages into this list. It looks as if PVS-Studio writes about IntelliSence. Thus, along with "our" messages

c:\users\ svn\viva64\vivawalker.cpp(1743): error V101:
Implicit assignment type conversion to memsize type.
error V112: Dangerous magic number 4 used: eeUtil::Nth(p, 4);.

the same list contains messages which are absolutely out of place:

"c:\program files (x86)\microsoft visual studio
line 1233 (col. 11): error: floating constant is out of range
"c:\program files (x86)\microsoft visual studio
line 1234 (col. 13): error: floating constant is out of range

Such messages are often quite senseless. Besides, they are generated not all the time but only in some rare and difficult-to-recall cases. Unfortunately, the only possible solution of this problem (in order to prevent PVS-Studio messages from mixing with those of IntelliSence) is to disable all the features of IntelliSence on the tab mentioned above.

If you do not have unnecessary messages from IntelliSence or they do not prevent you from handling PVS-Studio messages, you may leave IntelliSence enabled.

We hope that Microsoft will fix this issue in time and we will not need to disable IntelliSence.

P.S. There is a very good description of this settings tab in the Visual C++ team's blog.

Popular related articles
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…
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…
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…
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…
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…
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…
Appreciate Static Code Analysis!

Date: Oct 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…
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…
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…

Comments (0)

Next comments
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 →