views:

260

answers:

2

I'm developing a Windows Mobile app using the .NET Compact Framework 3.5 and VS2008, and for debugging using the Device Emulator V3, on Win7, and seem to have constant problems with Windows Mobile Device Centre (6.1) connecting.

Using the Emulator Manager (9.0.21022.8) I cradle the device using DMA in WMDC. The problem is it's so flaky at actually connecting that it's becoming a pain.

I find that when I turn my computer on, before I can get it to connect I have to open up WMDC, disable Connect over DMA, close WMDC down, reopen it again, and then it might cradle. Often I have to do this twice before it will cradle.

Once it's cradled it's generally fine, but nothing seems consistent in getting it to connect.

Connecting with physical devices is often better, although not always. If I plug a PDA into a USB socket other than the one it was originally plugged into then it won't connect at all. Often the best/most reliable connection method seems to be over Bluetooth, but that's quite slow.

Anybody got any tips or advice?

A: 

Try deleting the existing device partnerships. That has helped me in the past when WMDC/ActiveSync was playing up.

Go to Control Panel -> Sync Center and delete the device partnerships you see listed there. Then reconnect your device/emulator and when the WMDC window comes up, make sure you create a new device partnership (in my experience the connection/debugging becomes flakier when you choose to not setup a partnership).

tomlog
That's interesting actually, because I never create partnerships. Seeing as I'm never syncing anything, I figured it wasn't worth it. I'll try creating one.
Ira Rainey
OK, I've tried setting up a partnership, but now I remember why I didn't before. Running WMDC 6.1 on Win7 if I setup a partnership I get a blank dialog pop up whenever I connect the device, like it was supposed to be an error message that somebody forgot to put in. This comes up even if nothing is selected to sync. Removing the partnership gets rid of the erroneous dialog.
Ira Rainey
A: 

Another thing to point out about ActiveSync, I learnt this the hard way, I noticed the battery drains faster with ActiveSync, even if it is not in the cradle, it is actually running in the background, and whether it is a bug or not, not sure, but, it 'thinks' it is still in the cradle and continuously polling for the connection. Here's the link that explains it. And here's the temporary fix.

The way I dealt with it is to run a small C program that looks for the ActiveSync process and kill it each time I un-cradle the pocketpc.

Hope this helps, Best regards, Tom.

tommieb75
Thanks for that little tip. Should help save on the battery.
Ira Rainey