Processor jumps to 100% when looking at the Designer

[Alain Dekker]

I'm using VS 2005 with a C# app.

I've got a nice zippy computer, but whenever I switch between Form Designer
to code or between Form Designers, the processor jumps to 100%, the Designer
sort of blanks out, and then everything comes back to life after about
5-10s. Quite annoying. Jumping between the actual C# code modules for the
forms or classes is quick.

Is there anything I can do to prevent or improve this behaviour? What is the
IDE doing anyway? The action makes an impressive CPU mountain (as seen in
Task Manager).

Thanks,
Alain

 

[Alain Dekker]

Interesting thought. I do have the page file size set to 0MB (switched off),
but I've also got 2GB of RAM and almost never go over 1GB of Committ Charge.
Also, I get the same behaviour on another machine with a system managed page
file.

So don't think thats it. Its a VS 2005 problem as far as I can tell.

But, will try your suggestion and see if setting a Windows managed page file
helps.

Thanks,
Alain

 

[kndg]

I'm using VS 2005 with a C# app.

I've got a nice zippy computer, but whenever I switch between Form Designer
to code or between Form Designers, the processor jumps to 100%, the Designer
sort of blanks out, and then everything comes back to life after about
5-10s. Quite annoying. Jumping between the actual C# code modules for the
forms or classes is quick.

Is there anything I can do to prevent or improve this behaviour? What is the
IDE doing anyway? The action makes an impressive CPU mountain (as seen in
Task Manager).

Thanks,
Alain

It should come up quickly. But I have past experience where the IDE
suddenly becomes very slow. After careful examination, it turns out that
the Visual Studio cache folder was corrupted. You may try deleting below
folder (you should close the Visual Studio first),

C:\Documents and Settings\[Username]\Local Settings\Application
Data\Microsoft\VisualStudio\[version]

If it still doesn't work, try deleting below folder also,

C:\Documents and Settings\[Username]\Application
Data\Microsoft\VisualStudio\[version]

If you feel uneasy deleting the folder, you may try renaming it instead.

 

[Jeff Johnson]

I'm using VS 2005 with a C# app.

I've got a nice zippy computer, but whenever I switch between Form
Designer to code or between Form Designers, the processor jumps to 100%,
the Designer sort of blanks out, and then everything comes back to life
after about 5-10s. Quite annoying. Jumping between the actual C# code
modules for the forms or classes is quick.

Is there anything I can do to prevent or improve this behaviour? What is
the IDE doing anyway? The action makes an impressive CPU mountain (as seen
in Task Manager).

5-10 seconds seems a bit much. With a relatively complex form, I sometimes
see 3-4 seconds on my work machine, but far less at home (where I have a
beefier computer). I don't have an answer for you, but I feel your pain.

 

[Alain Dekker]

OK, maybe it was slightly exaggerated and it was 4-5s and not 5-10s! Still
pretty darn annoying...it must be VS 2005 re-caching something. Really the
IDE should have some sort of "dirty" flag or maybe have used a separate
thread because I hadn't changed anything at all on the GUI (just went back
to the form to get the name of a control). I even get it if I do nothing for
about a minute, then switch between code and designer!

Guessing there's no workaround...just a relatively minor bug int he
IDE...please be patient.

Thanks,
Alain