Hi, thanks for your reply.
"John Heitmuller." <john.heitmuller@jrfcorp.net> wrote in news:9b2c0e7a-
de37-4789-ac4f-9e0a02fa24f7@c33g2000hsd.googlegroups.com:
> The purest in me feels that making direct calls to the User32.dll
> builds in an OS dependency that may cause problems down the road. So,
> what I'm looking for is a way to accomplish the same thing with a
> single peer-to-peer send/receive VB.Net app using the .Net framework
> to manage the interprocess communications.
There is no reason why in remoting you could not host the client/server
in the same .exe. Your client just needs to expose an endpoints.
Unfortunately remoting out of the box is not bidirectional, so you'll
need to build some logic in the app to handle 2-way messaging.
> I've looked at the WCF docs in VisualStudio 2008. The parts of WCF
> that seem relevant to an example like SameBoxChat.exe look very
> similar to Remoting under 2.0 of the .Net Framework.
Similar, yet very different. WCF allows for multiple communications
channels and the ability to do bidirectional communications out of the
box.
WCF also has a Peer-to-Peer channel which maybe applicable in your
situation.
> I also agree with David's reply, ".NET Remoting seems a bit abstract
> and lacking in useful examples."
A bit perhaps - The company I work at use remoting extensively; it's not
mysterious once you build an application ro two.
> I was hoping that if it is possible
> to build a simple demo of a peer-to-peer send/receive VB.Net app using
> the .Net Framework, my example might prompt someone into do it. I've
> been programming for 20+ years. If I cannot figure it out, its not
> simple. But, I would love to be shown up and proved wrong. 8-)
If remoting is too complex, there are alternative frameworks available
such as Genuine Channels and RemObjects.

Signature
spamhoneypot@rogers.com (Do not e-mail)