View Full Version : MSVC 2005 .NET Intellisense issues

09-13-2006, 03:02 AM
It seems that 2005's intellisense does not update correctly when you update macros in a header file. Class Wizard also does not update correctly when you change the macro. Only way to fix it is to exit out of the IDE, erase the .ncb file for your project and restart the IDE.

Big bug there.

09-13-2006, 01:51 PM
I think form designer also has some bugs. It gives me circular ownership error for no reason.

09-13-2006, 02:38 PM
I've had some big issues with 2005 not recompiling header files unless I do a full build. This causes huge headaches if you make a change to a very small function's implementation inside a header file's class definition, start debugging, only to realize that its still using the old header file's code. Potentially this has something to do with the same thing?

09-13-2006, 11:01 PM
I wonder if we could submit a bug report to MS? 2005 should still be in the support phase and they are probably still working on updates for it. This failure to re-compile headers IMO is unacceptable. It can lead you to change code that is not incorrect simply because intellisense is showing the incorrect information.

In order to get my macros to work after changing them in the header I had to exit MSVS, erase the ncb file (Intellisense database file), and restart MSVS. Then it rebuilt the database. But I had to do this after every single alteration made to the header file. This is not good.

The really bad thing is that since ClassWizard uses the Intellisense database to get it's information, ClassWizard will also display incorrect information. The compiler actually is compiling your changes and your source file has changed, but ClassWizard and Intellisense are ignorant of the changes.

09-14-2006, 12:13 AM
I think you'd better go and check out Microsoft forum. Many of these bugs are discussed there.

09-14-2006, 03:08 AM
I knew it was a good idea to stay with 2003 for a little longer :p

09-19-2006, 03:04 PM
I remember telling MS after three days of VS05's release. No service pack since then. I would stay with 2003 but the toolkit is no longer given for free by MS simply because they want to promote VS05 Express? And they come out with a service pack for 2003 four days later. *confused*