Intermittent VS.Net Pauses during VB.NET code writing

2 Mar 2006 12:25 PM

genojoe

IN VS.NET 2005, I have a form with over 20,000 lines of code. Frequently,
both during debug or non-debug code editing, VS.NET freezes for up to 30 or
60 seconds to collect its thoughts. I think others may be experiencing this
problem if they are editing a class with a large amount of code. Here is how
I learned to deal with it.

I open the Windows Task Manager and set it to the Processes Tab and Sort by
CPU. I then highlight devenv.exe and watch its behavior. When it is the
first item in the list, I know I am frozen and just wait. When it moves down
the list, I can then begin (or resume) my editing. This solution does not
eliminate the pauses but it makes it easier to know when you can resume your
code development.

2 Mar 2006 12:48 PM

Brian Henry

turn off autosave recovery information it will stop that

Show quoteHide quote

"genojoe" <geno***@discussions.microsoft.com> wrote in message
news:6FB57E3D-755C-4BE5-944B-E9A67B4CE28F@microsoft.com...
> IN VS.NET 2005, I have a form with over 20,000 lines of code. Frequently,
> both during debug or non-debug code editing, VS.NET freezes for up to 30
> or
> 60 seconds to collect its thoughts. I think others may be experiencing
> this
> problem if they are editing a class with a large amount of code. Here is
> how
> I learned to deal with it.
>
> I open the Windows Task Manager and set it to the Processes Tab and Sort
> by
> CPU. I then highlight devenv.exe and watch its behavior. When it is the
> first item in the list, I know I am frozen and just wait. When it moves
> down
> the list, I can then begin (or resume) my editing. This solution does not
> eliminate the pauses but it makes it easier to know when you can resume
> your
> code development.
>

2 Mar 2006 3:28 PM

genojoe

Thanks. I was hoping for this type of response.

I did not know that Autorevover existed. Instead of turning off, I
increased it to 15 minutes.

Again Thanks.

3 Mar 2006 9:24 AM

genojoe

I have disabled autorecovery completely. With my large class, the pauses are
sufficiently frequent to make my crutch for seeing when the code again is
editable valuable to me.

This is especially true when doing code editing during debug.