Hi,

I am developing network real time application. While my device is in
the cradle my program binds to IP assigned by a host for ActiveSync
connection. So all communication is going through host machine and my
app is not working, I don't know yet why, network might be too slow or
my app can't recognize "firewall" propery.

Previously I was able to take the device out of cradle and debugger
would still work becuase activesync 3.8 supported ethernet connection.
However 4.0 & 4.1 don't support ethernet connection so I can't do that
anymore.

Is there a way to debug apps and not have IP addreess for host
connection.
Bluetooth & IR are too slow. I can have two ethernet cards on my
device.

regards
Milan

Re: debug/networking while in the cradle by MSenne

MSenne
Fri Jan 13 09:10:44 CST 2006

2 ethernet adapters on your Pocket PC? Would you mind sharing what
device that is because I'm very curious!

A lot of people are having this problem with WM5 devices because
Connmgr.exe kills WiFi and other network adapters in favor of RNDIS
when USB syncing. There is still no definitive post on the matter so
I can't really direct you anywhere else. It's a problem.

The easiest solution to Syncing without losing the connecting is using
Bluetooth, which you say is too slow.
One other way may be to use AirFix:
http://airscanner.com/downloads/airfix/airfix.html
which will kill connmgr.exe before it can kill your connection. May
work for debugging so you can try it.

Make sure you search through this newsgroup more, there may be more
information about that is helpful to you that I missed.
-MSenne


Re: debug/networking while in the cradle by milandi

milandi
Fri Jan 13 14:43:06 CST 2006

Hi,

I ahve problem with PPC2003 devices and new ActiveSync, I think this is
an AS4 issue not WM2005.

About two cards: I just have ordinary PPC + bought aditional ethernet
card for few bucks and pluged it in.

The trick I am using right now to make things work is that I put a
breakpoint at the very beginning of the program and when the breakpoint
is reached I close activesync connection. VS debugger uses wireless for
connection so at this point I can safelly remove device for cradle and
continue debugging. Device even doesn't have to be removed.
I am not sure if it helps with 2005.

Thanks for AirFix I will give it a try.


Re: debug/networking while in the cradle by MSenne

MSenne
Fri Jan 13 15:27:48 CST 2006

OK, you cleared up that 2 ethernet adapter pretty well. I really should
have guessed what you were talking about since I have an SDIO 802.11b
adapter its way to me for testing in a device with WiFi.

Anyway, are you saying you are debugging on your PPC via WiFi from
VS2005 without the aid of ActiveSync? Is the initial connection via AS
necessary to getting the debugger started? Is that technique
documented somewhere because I know that ethernet syncing was removed
in AS4.0 but I didn't know you could debug over WiFi and I haven't seen
this elsewhere.
Sounds interesting.
-MSenne


Re: debug/networking while in the cradle by milandi

milandi
Fri Jan 13 18:14:11 CST 2006

>
> Anyway, are you saying you are debugging on your PPC via WiFi from
> VS2005 without the aid of ActiveSync?
sort of. AS4 in neccessary to start FIRST debugging session. One
debugging is started there is no need for active sync because data is
going through ethernet. I can restart debuging. Change code, recompile,
start debugging again without having AS4 connection. After a while VS8
will figure out that AS4 is broken and then I have to do the trick
again.

> Is the initial connection via AS
> necessary to getting the debugger started?
yes, but just first time

> Is that technique documented somewhere because I know that ethernet syncing was > removed in AS4.0 but I didn't know you could debug over WiFi and I haven't seen
> this elsewhere.
no it is not documented, just accidental discovery (too much bear too
late I guess).

Do you have any idea why would application behavesdifferently when
connection is going through AS USB. I have really big app and not
enough time to figure out and 90& of code is not mine anyway) ?
My guesses is that network is slower and it times out on response (or
my app can't handle this network topology... ). Do you know about any
documentation about that ? I get same problems with emulator.

cheers
Milan