PROB WITH NETWORK CONNECTION. Help!

  • Thread starter Thread starter Hari
  • Start date Start date
H

Hari

Hi,

PLEASE KEEP PATIENCE AND READ THIS TO THE END
I've already posted on this issue but could find the proper
solution

APP : I use a socket connection in my app. When i get a phonecall
the socket connection gets closed automatically.

TASK : need to reestablish the connection when the phone call ends.

PROB :
1) Currently, don't have a device to check this. So I have to test
this all with the emulator
2) I can't simulate an incoming call on the emulator, so theres no way
that I can know when the phonecall ends
3) SystemState class that provides notifications is a WindowsMobile
class that can't be used for pocketpc. My app runs on both
WindowMobile and Pocketpc

ASSUMPTION: So I made an assumption that the network becomes
available when the phone call ends.

WORK : So I started using SystemProperty.ConnectionsCount(ignored the
case of PPC for now) property which changes when the network
connections count changes

PROB:
I found no option in the emulator which I can use to connect or
disconnect network

WORK : I started to cradle and uncradle the emulator, it changes
ConnectionsCount property, I handle the event and try to reconnect
when the count is more than 1

PROB: ActiveSync gives hell lot of probs when I'm cradling and
uncradling.
It does'nt actually connect, even when the status in device emulator
manager is shown as cradled.
Activesync version that I installed is 4.2
Some times it showsup a window on the desktop saying it cant connect
to the device because the device is not a Pocketpc
And some times it shows up in the emulator saying the active sync
version is an older one and that I should install a newer version
above 4.0

POINT TO NOTE:
Theres a little diff between Pocketpc SE emulator and Windows Mobile
5.0 Pocketpc emulator.
That is, PPC emulator connects through the socket even when its not
cradled, but WindowsMobile emulator need to be cradled(the active sync
connected) to connect to the socket

Now Gentlemen, I invite your suggestions for my post. I would be
grateful to any suggestions that can help me


Thanks,
Hari
 
The problem is really that you're trying to use the emulator. You *HAVE* to
invest in a real device or you will not get this to work right. You've
already wasted enough time to pay for the device with no problem.

Paul T.
 
And once you've bought a device, you wonder why the heck you didn't do
so before. Seriously, the emulators are really only suitable for real
basic testing.

Chris
 
And once you've bought a device, you wonder why the heck you didn't do
so before. Seriously, the emulators are really only suitable for real
basic testing.

Chris
Click to expand...

Thank You Paul and Chris,

And sorry for the delay in response. I'll definitely follow your
suggestion to buy a device, but for some reason it would take time.
Any how i'll wait till the time.

Hari
 
Spend the intervening time testing other parts of the application besides
network and phone functions. If there aren't any other functions, read your
last five copies of MSDN Magazine or learn about some aspect of .NET CF
programming that you don't know anything about, yet.

Paul T.
 
Back
Top