G
Guest
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.
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.