Why does VS 2008 pause awkwardly while editing?

[Michael A. Covington]

Often, while I'm typing text into VS 2008, there is an awkward pause during
which keystrokes are not recognized, though they still go into the buffer
and the letters that I'm typing appear when the pause is over.

This lasts 5 to 10 seconds.

Process Explorer does not show anything going to high CPU usage at the time.

I'm editing files that are on a network disk, and I wonder if Visual Studio
is using the same disk for some kind of swap space (as Adobe products are
apt to do when editing files on a network disk). Or what?

 

[Shekhar]

1. VS officially does not support projects on network for the fact that it
creates lot of intermediate files in the project locations and keep on
updating them. The network latency would definitely hit you badly in such
cases.
2. You may want to try turning off outlining (Ctrl+M,P) or Go to Edit -
outlining - stop outlining.

 

[RvGrah]

I have noticed the same thing... Seems a bit worse in larger vb apps
than in c#. Wish I had an answer for you, but I thought I'd at least
chime in to second the question. I've posted twice in this forum about
Visual Studio exiting debugging back to the user interface of the
program I'm debugging without in any way telling me anything went
wrong. This may be an issue in 64 bit installs only though. Got no
answers so far either time I posted.

Bob Graham

 

[Shekhar]

For VB being interpreted language, its obvious that you see the issue being
more prominent or worse with VB. Again VS officially doesnt not support
projects over network.


I have noticed the same thing... Seems a bit worse in larger vb apps
than in c#. Wish I had an answer for you, but I thought I'd at least
chime in to second the question. I've posted twice in this forum about
Visual Studio exiting debugging back to the user interface of the
program I'm debugging without in any way telling me anything went
wrong. This may be an issue in 64 bit installs only though. Got no
answers so far either time I posted.

Bob Graham

 

[Tom Shelton]

For VB being interpreted language, its obvious that you see the issue being

VB is no more an interpreted language the C# is. The problem with the VB
environment is usually the background compile.