Large source files and Syntax Color/Intellisense Problems in VS.Net

[Rick Strahl [MVP]]

I seem to have problems when working with large Windows Forms files. What
happens is that hte editor looses its syntax color highlighting and
Intellisense capability on large files. The code works - it compiles and
runs fine, but the syntax color highlighting goes away. All formatting blows
up too and the editor no longer helps with indentations.

Needless to say this is frustrating.

If I recompile then color returns but as soon as I type somtehing it goes
bad again.

Anybody else seen this before?

Other:
I've also noticed that I run into problems with specific components (or so
it seems anyway). I'm using ActiveReports from DataDynamics and as soon as I
open a report and edit that the entire source editing environment behaves as
above. If I close the report exit and come back in everything works fine
again.

The base scenario though occurs frequently even if no third party
controls/tools are involved.


I suspect this has something to do with the auto-generated code
InitializeComponent, but if the code compiles there should be no reason that
the editing environment shuts down in this manner?

Any ideas appreciated...

+++ Rick ---


--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/

 

[Simon Harvey]

I sometimes see what your talking about - the highlighting going missing. It
usually goes away if I close the file and open it again though.

It does seem that there is a bug in their somewhere. I'm still using VS 2002
though.

Simon

 

[Rick Strahl [MVP]]

Well, I have one project where it's happening consistently even on
relatively small files. Opening and closing doesn't help - well, the
coloring returns but as soon as I type it goes away.

Shutting down the project and then reopening works for a while.

In further messing around with this it seems that this potentially has
something to do with external components loaded somehow. The problem always
manifests after editing a form that has a bunch of custom controls on it
(SharpUi, ActiveReports or custom controls) for example.

Problem is when the problem starts it effects all source files not just the
ones that potentially have some problems with controls on them.

It's more than a little frustrating because when the editor 'looses' it it
looses it bad as all indentation stops - it becomes just about unusable.

This is VS 1.1...

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/