   C++ Express does not display a list of relevant functions and variables anymore?!
  Well when I would program in C++ Express before it would display a list of relevant functions and variables when I would type something like "std::" or "variable->" but I added some new APIs to my project and edited the properties. Now it does not do that anymore and I mis it! I'm not sure what I changed that caused it to stop working, does anyone know what it may be?   
  Visual Studio's C++ Intellisense is pretty brittle; C++ is a complex parse. You can try to clean the project and/or delete your .ncb files (in the same directory as the .vcproj or .sln, usually) -- this often helps.   ;  It worked! Thanks jpetrie! =D   ;Quote:Original post by jpetrieVisual Studio's C++ Intellisense is pretty brittle; C++ is a complex parse. You can try to clean the project and/or delete your .ncb files (in the same directory as the .vcproj or .sln, usually) -- this often helps.Seems like an appropriate place to ask this: do you guys all find that intellisense randomly stops working for whole minutes at a time?  I get it fairly frequently and it's amazing just how irritating it becomes.  I also noticed that it craps out when you make a typo (which makes sense), except that when you correct that mistake, it still doesn't work.Is there any way to improve the stability of intellisense?  I've googled around on this several times before and I remember finding a submission to the Visual C++ Express team that detailed the problem.  They even replied on it but pretty much said nothing's going to be done about it for the foreseeable future.Does this behaviour exist in the pro versions of Visual C++, too?[Edited by - SeymourClearly on May 14, 2009 12:36:29 PM];  Pretty sure I read somewhere vs2010 is supposed to have much improved intellisense for c++ especially.  But it is identical in pro and express versions... the real difference between the versions is the packages (addins, and all the little side bars you get) that are installed for the core studio, and things like project templates and mfc.  The software itself doesn't change, they just include or exclude standalone packages that add functionality to the core program.   ;Quote:do you guys all find that intellisense randomly stops working for whole minutes at a time?Not sure if this is actually what you're experiencing... but I've noticed that behavior when I've written code that won't compile. Once I fix the mistake it comes back. Basically, I use Intellisense not working as a clue that what I've just written is invalid somehow. It's annoying, because sometimes I don't care and want to keep writing. If I forget to include a header and first start using a class for example, that kills Intellisense for the rest of everything.   ;  Hey guys.@popsoftheyearYeah, I get how the upgrades differ in terms of features, I just wondered if perhaps the intellisense was more up-to-snuff there, but what you say about the software itself not changing, makes sense.@y2kiahAha, see I get that as well and as I said above, that makes sense to me.  What doesn't make sense is that I can have code that compiles and links correctly, gives the correct results at runtime and still has no intellisense.  If I've made a simple syntax error somewhere, for example a missing semi-colon, then add it back in and compile the program, the intellisense will still not work.Sometimes I've even gone as far as having to clean a solution, rebuild it, close and re-open VS and the intellisense is still MIA.  It randomly starts working again a few minutes later (even when I've left the code entirely alone).  No other programs running, no CPU usage anywhere except system idle process and no disk access.I'll have to try deleting the ncb file next time (thanks for that idea Josh) and see if that helps.   ;  I get that quite often. Deleting the .ncb files always seems to help (doing so forces the compiler to regenerate its intellisense info from scratch).Quote:What doesn't make sense is that I can have code that compiles and links correctly, gives the correct results at runtime and still has no intellisense. If I've made a simple syntax error somewhere, for example a missing semi-colon, then add it back in and compile the program, the intellisense will still not work.Why does that suprise you? If you think about the way C++ is structured (no module system and the preprocessor) you'll come to the conclusion that providing intellisense is an even more difficult task than parsing the language. A single header file may be included from multiple places - and may be parsed differently each time it is included depending on what was #defined or declared prior to its conclusion; a single header file may even be included multiple times in the same translation unit.;  The actual event doesn't surprise me but the outcome of not having intellisense working for entire minutes at a time, does.  I understand it's a complicated process, although I'll be the first to admit that I can't fully appreciate just how complicated it gets, but it does seem a bit odd that it totally stops responding altogether for sometimes up to 5 minutes.Thanks for backing up the ncb idea though.   ;  I have a project that contains some template code and includes a couple of boost headers. Whenever I'm in one of those compilation units, Intellisense thinks I'm in namespace boost::boost::boost::boost::boost::boost::boost::boost::boost::boost ....   