Code completion troubles with MSVC 2003

Printable View

08-11-2008
Bajanine

Code completion troubles with MSVC 2003

I went through some code and changed some structure member names in my source code. Now when I try to use the code completion feature it doesn't give me the new names only the old ones. I tried 'Build | Clean Solution' but that didn't fix it. Anyone who uses Visual Studio 2003 have any ideas on how to fix this?
08-12-2008
Bajanine

Well, I finally got a clue and just created a new project, added all the source files to the project hit rebuild and everything works now.
08-12-2008
VirtualAce

IntelliSense is known to be slow and/or half broken in 2003. Also half the time the function browser doesn't work which is very annoying.

In MSVS 2005 both IntelliSense and the function browser are a bit iffy as well.
08-12-2008
Bajanine

I just figured out all I had to do was delete the *.ncb file from the project to fix the problem. When I started having trouble the file was over 1700KB after deleting and reloading the project it is only 331KB.
08-13-2008
Codeplug

Been using Visual Assist for years now - work's good.

www.wholetomato.com

gg
08-13-2008
Mastadex

Quote:

Originally Posted by Codeplug

Been using Visual Assist for years now - work's good.

www.wholetomato.com

gg

VisualAssistX (VAX) is a nice tool but it also has its limitations. because its so thurough with its indexing, it has a hard time parsing files over 8000 lines of code. It will often fail when it reaches that size. not only that, I wouldn't really suggest it when using the .NET framework. It failed on me many times when I coded large C++ programs that use the .NET framework.

Take it with a grain of salt, but it still is the best tool out there, IMO.
08-13-2008
vart

Quote:

it has a hard time parsing files over 8000 lines of code.

just another reason to avoid such huge files
08-13-2008
matsp

Quote:

Originally Posted by vart

just another reason to avoid such huge files

Not always your choice tho' - but I agree that no one should WRITE such large files.

--
Mats
08-21-2008
Mastadex

I dont make it my intention to work with files that big, I'm sort of forced to. But I agree, smaller files are easier on VAX and your brain.
08-21-2008
VirtualAce

Any time you have intellisense problems that just won't go away or you get the error that your project cannot open such and such NCB file and thus class browser will not be available you should delete the NCB and restart MSVS.