Home All Groups Group Topic Archive Search About

Unwelcome forced pauses during code development in VS 2005

Author
17 Jan 2006 3:26 AM
genojoe
I have a Windows Form VB.NET application with many, many menu items, and
thousands of lines of code in the form class. I have upgraded it to VS 2005
and am now very unhappy with periodic delays during code development.  I
rarely have the design window for the form open in VS 2005; only the vb code.
As I change between VS code panes or begin and end a debugging session,
frequently devenv.exe hogs up the CPU (Information from Task Manager) for
what appears to be minutes at a time.  The earlier version of VS only had
this problem when I changed between design  panes.  My computer has 1 gig of
memory.  The processor is an AMD 3400+ (2.41 GHz)
Are other people experiencing this same problem with VS 2005?   Any
thoughts?  This annoying periodic delay almost makes real-time code editing
not worth it.  Sitting there staring at the screen during these update
periods is not fun.

Author
17 Jan 2006 12:19 PM
Ken Tucker [MVP]
Hi,

        Submit a bug at the msdn product feed back center.

http://lab.msdn.microsoft.com/productfeedback/

Ken Tucker
------------------
Show quoteHide quote
"genojoe" <geno***@discussions.microsoft.com> wrote in message
news:EE3B5913-C42B-4576-80FD-F2EA92747890@microsoft.com...
>I have a Windows Form VB.NET application with many, many menu items, and
> thousands of lines of code in the form class. I have upgraded it to VS
> 2005
> and am now very unhappy with periodic delays during code development.  I
> rarely have the design window for the form open in VS 2005; only the vb
> code.
> As I change between VS code panes or begin and end a debugging session,
> frequently devenv.exe hogs up the CPU (Information from Task Manager) for
> what appears to be minutes at a time.  The earlier version of VS only had
> this problem when I changed between design  panes.  My computer has 1 gig
> of
> memory.  The processor is an AMD 3400+ (2.41 GHz)
> Are other people experiencing this same problem with VS 2005?   Any
> thoughts?  This annoying periodic delay almost makes real-time code
> editing
> not worth it.  Sitting there staring at the screen during these update
> periods is not fun.
>