How to get IntelliSense to reliably work in Visual Studio 2008

V

12

40

Does anyone know how to get IntelliSense to work reliably when working in C/C++ projects? It seems to work for about 1 in 10 files. Visual Studio 2005 seems to be a lot better than 2008.

Edit: Whilst not necessarily a solution, the work-around provided here:

How to get IntelliSense to reliably work in Visual Studio 2008

Is probably the best bet if I want a decent IntelliSense system.

Videogenic answered 2/9, 2008 at 13:13 Comment(0)

M

27

I've also realized than Intellisense is sometime 'lost', on some big project. Why? No idea.

This is why we have bought Visual Assist (from Tomato software) and disabled Intellisense by deleting the dll feacp.dll in the Visual studio subdirectory (C:\Program Files\Microsoft Visual Studio 8\VC\vcpackages)

This is not a solution, just a workaround.

Margay answered 2/9, 2008 at 14:2 Comment(3)

+1 for how to disable the intellisense. The macro's I used for disabling in 2005 didn't work anymore in 2008. – Probationer 8/11, 2010 at 9:30

I read elsewhere that just deleting that dll should be handled carefully, creating a folder named "Solutionname.ncb" should be preferred. Results in annyoing error messages at every startup though. And +1 for mentioning VAX. – Inainability 2/3, 2012 at 11:27

This is still good advice as of VS2010 since intellisense in VS2010 is very slow (although now it's possible to disable intellisense using the config page in VS) – Harwell 26/3, 2012 at 13:3

M

32

Native C++ intellisense does not work reliably in any version of Visual Studio. I find there are two common problems:

1) Header file paths are not set-up correctly. When you find a type where intellisense is not working, use the IDE to click through each header file to find the one containing the type. (Right click on #include and select Open Document...). If this fails before you get to the file which declares the type then this is your problem. Make sure header file search paths are set-up correctly.

And,

2) The intellisense database is corrupt. This happens ALL The time. You need to close the solution, delete the .ncb file, and then reopen the solution. I posted the macro I use for this in answer to another question here.

The preprocessor can also confuse intellisense - so make sure any #defines during build are also available to intellisense. Other than that, I don't know what else can break it. I've not seen any particular issues with forward declarations.

Mossbunker answered 2/9, 2008 at 13:33 Comment(4)

Thats a helpful solution to delete the ncb file. :) – Gargoyle 6/10, 2009 at 18:57

Note: Intellisense was fixed in VS2010. – Telemetry 5/12, 2010 at 17:19

Damn it, Microsoft! I have 544 #includes in this project (not counting the nested #includes in them and countless #defines.) Fix your s&^*! Thanks to the poster for the idea. – Mug 25/11, 2013 at 0:8

+1 deleting the sdf (VS2010's new extension for what what was ncb in '08) worked for me. I closed the VS solution, deleted the solution's SDF file, re-opened the solution, re-built the solution, and voila. – Sublet 9/12, 2013 at 19:55

M

27

I've also realized than Intellisense is sometime 'lost', on some big project. Why? No idea.

This is why we have bought Visual Assist (from Tomato software) and disabled Intellisense by deleting the dll feacp.dll in the Visual studio subdirectory (C:\Program Files\Microsoft Visual Studio 8\VC\vcpackages)

This is not a solution, just a workaround.

Margay answered 2/9, 2008 at 14:2 Comment(3)

+1 for how to disable the intellisense. The macro's I used for disabling in 2005 didn't work anymore in 2008. – Probationer 8/11, 2010 at 9:30

I read elsewhere that just deleting that dll should be handled carefully, creating a folder named "Solutionname.ncb" should be preferred. Results in annyoing error messages at every startup though. And +1 for mentioning VAX. – Inainability 2/3, 2012 at 11:27

This is still good advice as of VS2010 since intellisense in VS2010 is very slow (although now it's possible to disable intellisense using the config page in VS) – Harwell 26/3, 2012 at 13:3

I

6

It looks like there's hope on the horizon for those of us unable to obtain Visual Assist:

Rebuilding Intellisense

Intraatomic answered 29/5, 2009 at 18:18 Comment(1)

But no support for C++/CLI in the first release of VS2010 :/ – Operative 1/7, 2009 at 9:49

S

4

Do you have any add-ins installed (or uninstalled)? I find that effects my intellisense.

Besides that just making sure your Tools->Options->Text Editor->All Languages "Auto List Members" and "Parameter Information" are checked off.

Shows answered 2/9, 2008 at 14:1 Comment(2)

Thanks, this helped me figure out why Intellisense mysteriously stopped working! – Desman 10/1, 2010 at 16:45

My "All Languages" settings showed green squares instead of checkmarks (presumably because they were set for only some of the languages). Clicking on them so they were checked fixed the problem for me. – Elke 19/4, 2012 at 20:10

T

2

I don't use VS2008 for C++, only VB & C#, but I find that when intellisense stops working (true for VS2003/2005/2008) it's because something in the project/file is broken - usually a bad reference or code.

VB and C# have much better intellisense support due to the ability to reflect on the referenced assemblies to build the intellisense tree.

C++ has to walk the include files for function prototypes, and if the paths are not correct it will not find all the prototype headers.

Transmittance answered 2/9, 2008 at 13:36 Comment(0)

B

2

My fix to itellisense was required after that awful refactor utility minced my code. The problem was a class header file that included an #include of itself. The recursive reference destroys itellisense. A symptom of this is if itellisense can see other classes but not the current one. Also:

Use #pragma once to eliminate duplicate header loads

If the project now takes a very much longer time to load, that itellisense trying to make sense of the conflict that is causing then lack of completion support.

Often it is only one class object that is affected, This shows you what files (usually headers) to look at.

Bimbo answered 15/10, 2010 at 1:3 Comment(0)

V

1

@John Richardson / @Jonathan Holland

My includes are setup correctly, no problems there. I've also tried the NCB rebuild several times but it never fixes it 100%.

I have a feeling it may be to do with forward declarations of classes. e.g. to reduce the complexity of includes in header files we normally do something like:

class MyPredeclared;

class SomeOtherClass
{
private:
    MyPredeclared* m_pPointer;
}

I wonder if that screws it up? Any other ideas? It definitely gets worse the larger your project gets.

Videogenic answered 2/9, 2008 at 13:41 Comment(0)

C

1

I had a very annoying problem, intellisense was working only in some files, without any evident reason... it took me a couple of hours of digging through google, but I finally understood that the reason was indeed recursive reference! I was using the:

#ifndef CLASS_H
#define CLASS_H
...
#endif

to avoid redefinition of symbols, and this sometimes breaks intellisense in big projects.

But it is enough to comment the ifndef-define-endif and put a:

#pragma once

at the beginning of the header files to still avoid redefinitions and have Intellisense working again =)=)

At least, this worked for me, hope it's useful...

Cheers Francesco

Carbolated answered 2/6, 2011 at 9:51 Comment(0)

I

1

I have recently studied Intellisense in VS2008, as I'm developing a rather large C++ numerical linear algebra library where templates and such are used extensively. Intellisense stopped working shortly into the project and I sort of gave up, but now it became really annoying without it so I set to investigate. This is what I found out:

Assuming there is a file(s), containing code that "breaks" Intellisense,

if header files that break Intellisense are in the project, but are not #included, it still works in the rest of the files
if they are included, but no type declared inside is used, it still works
if they are included and a type declared inside is used, it might still work a bit (no Intellisense for members, no Intellisense after occurrence of given type, but at least global names and argument info before)
if Intellisense is broken in one .cpp file, it can still work in the others where the problematic code is not included or used (but i imagine if it crashes bad, it will get disabled for the whole project, although that did not happen to me)
Intellisense seems to be updated after successful compilation (sometimes not before)
putting broken code inside any of #if 0, /* .. */ or // seems to put Intellisense at ease

From the C++ features I used, actually only a few break Intellisense:

comparison with '>' or '>=' in template parameter (e.g. static_assert<(size > 0)>)
- not solved by using double parentheses (static_assert<((size > 0))> does not help)
- solved by using '<' or '<=' instead (static_assert<0 < size> works)
- solved by storing the value in enum and using that to specialize the template
explicit function template specialization disables argument info (e.g. function<type>(args))
- probably unable to solve (maybe wrap in a macro), but I can live with it being broken
instantiation of template member type, such as Matrix::MakeMatrixType<3, 3>::Result r;
- kind of hard to figure out exactly why this happens (likely because of use of Eigen)
- workaround by moving such code in a separate .cpp where IS won't work (not always possible)

It would seem that some of those problems are due to some "simplified" parsing, which is less strong than a proper C++ parser. With the above information at hand, a "reliable" method of making Intellisense work in an existing code:

Set up an empty project (a console app), create Main.cpp with dummy void main() {} in it.
Include one of your broken header files, and math.h
Build (it must compile, in order for Intellisense to update reliably)
Test whether Intellisense is working by typing e.g. sin( and seeing if argument help pops up. Sometimes, this would work, but member help wouldn't - so try that as well.
Make an instance of something in the header file, build, see if that manages to kill IS.
Remove code from the culprit file and go to step 3
After finding and fixing problematic code, put back code removed in step 5, try again
After making a whole class work well, make an instance of the next class, and so on ...

I found it easy this way to pinpoint locations of code that made problems (I realize that this might be unfeasible for really large projects, in my case only a single file out of 97 made problems). Note that 'Build' here refers to compiling, the linking stage does not need to finish, so unresolved externals are ok, the IS should update regardless.

Another method of updating IS (other than building) is to save everything, close workspace, delete .ncb file and reopen it. Then wait for 'Updating Intellisense ... (N)' to disappear from the status bar (N counts towards zero, if it doesn't go all the way, it kind of shows progress where problems occurred). I found this rather tedious.

Indefinable answered 5/12, 2013 at 10:26 Comment(0)

H

0

About this problem i've notice something interesting (on Visual Studio 2010): to solve this problem i've changed #include sintax in my header files, before was (old project done with VS 2005 and reopened using VS 2010):

#include <myfile.h>

and i fix this with:

#include "myfile.h"

After intellisense start working correctly! I hope this can help!

Heartwarming answered 28/3, 2011 at 7:45 Comment(0)

M

0

I had to reset the settings...

C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE>devenv.exe /ResetSettings

thread on this here

Meggie answered 11/5, 2011 at 8:33 Comment(0)

D

0

The problem is with the .vcproj files.

You will find if you switch to release mode from debug mode, build, then try intellisense it often works.

Close Visual Studio. If you search for the .vcproj files in your project, edit them and search for the first two instances of AdditionalIncludeDirectories. The value for this should look something like "..\,....\" rather than "../..".

Reopen your project, let the Intellisense finish building, then it should be fixed.

Dawn answered 12/2, 2014 at 11:33 Comment(0)

Recommended topics

Hot tags