Geek Answers Handbook

Why is WMDC / ActiveSync so flaky?

I am developing a Windows Mobile application using the .NET Compact Framework 3.5 and VS2008 and for debugging using a V3 device emulator on Win7 and it seems to constantly encounter a Windows Mobile Device Center connection (6.1).

Using the emulator manager (9.0.21022.8) I substitute the device using DMA in WMDC. The problem is that it is so jagged that it actually connects it, becoming a pain.

I found that when I turn on my computer before I can connect it, I need to open WMDC, disconnect Connect over DMA, close WMDC down, open it again, and then it can be connected. Often I have to do this twice before he is cradled.

After it fit in general, it was perfect, but nothing seems consistent in connecting it.

Connecting to physical devices is often better, although not always. If I connect the PDA to a USB connector other than the one from which it was originally connected, it will not connect at all. Often the best / most reliable way to connect seems to be via Bluetooth, but it's pretty slow.

Anyone have any tips or advice?

+3
source share
3 answers

I thought I would add a few notes so that I could close it. In general, I did not find the following to make it more stable:

1) . , , .

2) , ( USB) USB-, , . , .

3) , WMDC DMA, WMDC, DMA, .

4) , , , ActiveSync, . , , , , , , .

- - , , .

+1

. , WMDC/ActiveSync.

→ , . / , WMDC, , ( / , ).

0

, ActiveSync, , , ActiveSync, , , , "", . , . fix.

The way I dealt with this is to run a small C program that looks for the ActiveSync process and kill it every time I take off my handheld computer.

0
source

More articles:


All Articles