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?
Favorite Quote:
>For that reason someone invented C++.
BLASPHEMY! Begone from my C board, you foul lover of objects, before the gods of C cast you into the void as punishment for your weakness! There is no penance for saying such things in my presence. You are henceforth excommunicated. Never return to this house, filthy heretic!
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.
Favorite Quote:
>For that reason someone invented C++.
BLASPHEMY! Begone from my C board, you foul lover of objects, before the gods of C cast you into the void as punishment for your weakness! There is no penance for saying such things in my presence. You are henceforth excommunicated. Never return to this house, filthy heretic!
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.
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.
Favorite Quote:
>For that reason someone invented C++.
BLASPHEMY! Begone from my C board, you foul lover of objects, before the gods of C cast you into the void as punishment for your weakness! There is no penance for saying such things in my presence. You are henceforth excommunicated. Never return to this house, filthy heretic!
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.Originally Posted by Codeplug
Take it with a grain of salt, but it still is the best tool out there, IMO.
Founder and avid member of the Internationsl Typo Associateion
just another reason to avoid such huge filesit has a hard time parsing files over 8000 lines of code.
All problems in computer science can be solved by another level of indirection,
except for the problem of too many layers of indirection.
– David J. Wheeler
Not always your choice tho' - but I agree that no one should WRITE such large files.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
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.
Founder and avid member of the Internationsl Typo Associateion
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.
