By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,013 Members | 1,210 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,013 IT Pros & Developers. It's quick & easy.

Client/Server Messaging with PocketPC

P: n/a
db
I need to write some basic code that will let me send messages to/from
a PocketPC. In the past, when I was using VB6, I did this using the
Winsock control and setting one machine as the client and the other as
the server. I assume I could take a similar approach here, but wanted
to see if anyone could give me any suggestions as to where to start.
I'm using .NET 2003 and Windows Mobile 2003 if that helps. This is
nothing really complex, I just need to send basic command strings from
the PocketPC back to the desktop - the PPC will essentially be a remote
control for the desktop application. Thanks.

-Dave

Nov 17 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
db,

Have you taken a look at the System.Sockets namespace?

Also, you might want to consider using Remoting here, if you have .NET
on both sides. I'm not sure what the support for remoting is in the compact
framework, but if you have it, I would use it, as it woud give you much more
flexibility in the kinds of messages you can send.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"db" <da*************@hotmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
I need to write some basic code that will let me send messages to/from
a PocketPC. In the past, when I was using VB6, I did this using the
Winsock control and setting one machine as the client and the other as
the server. I assume I could take a similar approach here, but wanted
to see if anyone could give me any suggestions as to where to start.
I'm using .NET 2003 and Windows Mobile 2003 if that helps. This is
nothing really complex, I just need to send basic command strings from
the PocketPC back to the desktop - the PPC will essentially be a remote
control for the desktop application. Thanks.

-Dave

Nov 17 '05 #2

P: n/a
db,

Have you taken a look at the System.Sockets namespace?

Also, you might want to consider using Remoting here, if you have .NET
on both sides. I'm not sure what the support for remoting is in the compact
framework, but if you have it, I would use it, as it woud give you much more
flexibility in the kinds of messages you can send.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"db" <da*************@hotmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
I need to write some basic code that will let me send messages to/from
a PocketPC. In the past, when I was using VB6, I did this using the
Winsock control and setting one machine as the client and the other as
the server. I assume I could take a similar approach here, but wanted
to see if anyone could give me any suggestions as to where to start.
I'm using .NET 2003 and Windows Mobile 2003 if that helps. This is
nothing really complex, I just need to send basic command strings from
the PocketPC back to the desktop - the PPC will essentially be a remote
control for the desktop application. Thanks.

-Dave


Nov 17 '05 #3

P: n/a
db
Nicholas, thanks for the quick response. I'm just starting to go
through the Sockets info in the .NET help. Any limitations, concerns I
should be aware of? I think I'd rather go with TCP over UDP since the
data transfer seems more robust. Thoughts?

Nov 17 '05 #4

P: n/a
db,

If you can afford to have packets drop, then go with UDP. Otherwise, go
with TCP. It all depends on the requirements of your application.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"db" <da*************@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
Nicholas, thanks for the quick response. I'm just starting to go
through the Sockets info in the .NET help. Any limitations, concerns I
should be aware of? I think I'd rather go with TCP over UDP since the
data transfer seems more robust. Thoughts?

Nov 17 '05 #5

P: n/a
Hi,
I'm not sure what the support for remoting is in the compact framework,


Nop, it's not supported :(

A TCP connection is the way to go.

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
Nov 17 '05 #6

P: n/a
db
I'm exploring some TCP code now by trying to modify some sample code.
The TCPListener I'm using on the Server side doesn't appear to be
event-driven. For the way I'm approaching this, it'd be great to have
events for "ConnectionRequestReceived" and "DataReceived." Can I try
to implement this behavior myself?

Nov 17 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.