Visual studio hogging CPU and memory for this PPC project...

[tf2_lags]

Hi,

I have an old VS 2003 project - VB.NET with compact framework. For some
reason, since the conversion, this project hogs memory and cpu bad. It
takes 3 minutes to go from code to form view.

I have tried many ways, including the many faqs on the NET to speed this up
but having no luck. Do you know what might be causing this? My VS 2005
desktop apps don't do this.

Here are some points about the project:

It is 1 form with 15 panels that I hide and show
78 pictureboxes
10297 lines of code

thanks!
B

 

[Simon Hart [MVP]]

That is your problem for a start, 78 pictureboxes! gosh what is your app
doing with them?, and 15 panels. Do the panels contain the pictureboxes? I am
suprised your form loads at all on the device.

You didn't say which version of VS you've upgraded to. Natuarally, VS 2005
requires more memory and CPU over 2003 and likewise VS 2008 is similar
although not quite as big a jump going from 2003 to 2005.

 

[tf2_lags]

That is your problem for a start, 78 pictureboxes! gosh what is your app
doing with them?, and 15 panels. Do the panels contain the pictureboxes? I
am
suprised your form loads at all on the device.

That's the way we had to code it back during PPC 2002 and 2003 because
otherwise, it would take each form 8 seconds to load when you clicked a
button.

So what would you advise? Should I break the panels up into forms? Cut
back on pictureboxes?

 

[Simon Hart [MVP]]

It is difficult for me to suggest how to code your form as I don't know what
you are trying to achieve. What are you trying to achieve with this form with
lots of panels? some kind of Wizard?

 

[tf2_lags]

Like I mentioned... we used panels because forms used to slow down between
screen switching. Panels were much quicker.

my entire project is panels instead of multiple forms.

 

[Simon Hart [MVP]]

I wouldn't consider this to be quicker, the initial load time must be pretty
slow.

Anyway this aside, VS 2005 demands alot more CPU and memory than VS 2003
purely because it's doing alot more than VS 2003.