>Intellisense is a good bet. Quick test - try deleting the .ncb file for the
>project. If that changes the behavior (for better or worse), then it's
[quoted text clipped - 3 lines]
>
>http://blogs.msdn.com/vcblog/archive/2007/11/12/performance-improvements-in-visu
al-c.aspx
I had tried deleting the .ncb files but didn't notice any difference.
Also while trying to work I keep seeing the caption saying "Microsoft Visual Studio (Not
Responding)".
I read the blog. The last two posts today say:
<quote>
Anyone here who tried the patch with VS2005 Professional? It seems that the .msp file of the patch
does not contain the product code of VS2005 Prof. and therefore the patch refuses to install.
Jens, I have the same problem with Professional...
</quote>
This is what I'm running also and it looks like it won't work. So Microsoft can't fix this? I can't
write code for their operating system if they won't. This is dumb.
the blog also says:
<quote>
To give you a feel for the scope of the changes we made to address these issues in VS2005 and
VS2008, this work touched 46 source files across three DLLs. Overall, 4664 lines of code were
changed or added. I would like to take this opportunity to give you a bit of insight into the
nature of problems we identified and the solutions we implemented.
</quote>
The project I'm working on has 4 dlls and hundreds of source files and probably over 100,000 lines
of code. I'm amazed that Microsoft would release such crap and that they can't fix this.
Sam
Ben Voigt [C++ MVP] - 15 Nov 2007 21:54 GMT
>>Intellisense is a good bet. Quick test - try deleting the .ncb file for
>>the
[quoted text clipped - 21 lines]
> Jens, I have the same problem with Professional...
> </quote>
I installed it on VS2005 Professional SP1, no Vista patch (this computer is
running XP).