Can't get Intellisense to work very well with our codebase since upgrading from (I think) 1246. Contrived snippet of code follows that shows the kind of thing we're seeing. Will be going back to 1246 later this week as a sanity check...
void MakeFruit ( ) { // Typing 'TF' displays (TFruit,TFruit1) with question mark icon // Typing 'NS' displays both namespaces with question mark icon // Typing 'NSINNER::' gets all the Intellisense correctly } } }
------- Contrived Code --------
stdafx.h is the standard console mode appwizard generated file. Using VS.Net 2003 on WinXP SP2 (English/UK locale).
Should have mentioned - the problem observed with the contrived code isn't that major (it just puts up the wrong icon for the symbols in the Intellisense popup) but is symptomatic of the problems we see with our codebase where Intellisense only displays a subset of the available symbols in some cases but generally works OK if a fully qualified symbol name is used.
there are actually two different types of listbox involved.
the ones with question mark icons used to have tomato icons, and are suggestion listboxes: http://www.wholetomato.com/products/features/suggestion.html?more=yes by design these will never show you all of the symbols, only VAX's educated guess at what you are currently typing. normally these are quite accurate and save me a load of typing
hopefully this helps to explain what you are seeing. by the sounds of it VAX is actually behaving correctly. you just have to know what it is doing for this to make sense