Tips for improving debug performance?

[Guest]

Ah, the good old days of VS2003...

I am very happy with the performance of my application under CF2, however,
development and debugging is much slower.

First, the emulator is abysmally, almost unusably slow. I have an
application heavy in web service calls and xml, and the emulator is now an
absolute last resort. Under VS2003 I occasionally used the emulator, but
most commonly used the device with a WiFi connection. Now I no longer have a
WiFi sync option.

So, I am doing most of my debuggin on the device via USB sync. Every time I
start the debug session however, I have to wait as the CF library, SQLMobile
library, and debug libraries are transferred to the device.

Is there any way to improve the performance of the debug process? I am
running an Athlon XP 2500 with 1gb RAM; will a faster or dual core PC provide
much improvement in either the emulator or the USB sync scenario?

What methods has everyone else used to get better performance while
developing?

Thanks all!

 

[William LaMartin]

My experience with debugging using the emulator is that it takes a long time
for everything to load (AMD Athlon 64 dual core with 2 GB RAM).

However, when I debug using the device connected via USB cradle to my much
slower laptop, everything is fairly fast in that the compact framework does
not have to be loaded since it is already on the device. This is for fairly
simple applications.

I also takes much, much longer to load an XML file into a dataset and
display it in a datagrid using the emulator than in the device.

 

[n33470]

pmoon,

Do you exit the emulator when you stop debugging? If so, you can
speed up the deployment process by leaving the emulator running, when
you stop debugging. If you leave the emulator running, you will not
have to redeploy the common stuff for subsequent debug sessions.

Just a thought.

--steve