Geek Answers Handbook

Visual Studio 2005 - IntelliSense Update

I have been having problems with my Visual Studio 2005 IntelliSense for some time. It worked fine, but for some reason, "IntelliSense Update ..." seems to no longer be suitable for the solution I'm working on - it just gets stuck somewhere in about 3 progress bars and blocks one of my precious processors for eternity. Deleting the .ncb file of my solution and doing the full Clean subsequently did not help. The "update" just got stuck again.

The project I'm working on is a fairly large C ++ solution with 50+ projects, quite a few classes of templates (as of late) and overall quite complicated. I do not know what impact this may have on IntelliSense. Visual Studio 2005 Service Pack 1 (SP1) and all the fixes that rely on it are not (we had huge problems with this, so we haven't migrated yet).

Any answer is much appreciated on this. Gives me creeps ..

Cheers
\ Bjorn

+6
visual-studio visual-studio-2005 intellisense
source share
4 answers

I found that the best solution for Intellisense in VS2005 is to install Service Pack 1 (SP1), and then this hotfix: 947315 . It has the added benefit of eliminating most problems with multi-core builds.

This fix also includes the ability to control Intellisense with macros. More details here .

To make SP1 friendlier for existing code, you can also check this patch to compile the template: http://support.microsoft.com/kb/930198

+5
source share

Rename "C: \ Program Files \ Microsoft Visual Studio 8 \ VC \ vcpackages \ feacp.dll" to something else (eg. Feacp.bak) to disable Intellisense.

I recommend getting Visual Assist X to compensate for this (it also has a number of other useful features).

+8
source share

Intellsense is problematic. Very problematic. When it works, it's great, but more often than not it will cause more problems than it costs. It will freeze, it will analyze files while you try to compile the code, and, as a rule, VC 2005 sometimes runs like a dog. As suggested in a previous post, disable intellisense (and choose a potential alternative - I also support VAX).

Presumably, the fix and SP1 provided by MS will fix some problems with intellisense, but not all. We saw minimal help from them where I work. You better disconnect it and rely on something else.

I feel that the slowness comes from the size of the projects. It seems that it might fall in this case.

0
source share

Here is the only solution that works for me.

0
source share

More articles:


All Articles