Inter Process Communication

[A.M]

Hi,

What is the best way to implemet Inter Process Communication in .NET ?

I developed two programs and I want to have them talk to each other.

Thanks,
Alan

[Richard Blewett]

It depends on what degree of communication you need. If they just need
coordinate their actions you can use a named Mutex (see the System.Threading
namespace).

If you need proper calling with params, etc the only out-of-the-box solution
is remoting (System.Runtime.Remoting and friends).

However, a while back I wrote a wrapper round shared memory that may help
you do what you want - you can find it here (watch out for line breaks):

http://staff.develop.com/richardb/do...aredmemory.zip

HTH

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

"A.M" <no*****@online.nospam> wrote in message
news:uT****************@TK2MSFTNGP12.phx.gbl...

Hi,

What is the best way to implemet Inter Process Communication in .NET ?

I developed two programs and I want to have them talk to each other.

Thanks,
Alan

[A.M]

Thanks for help.

So we don't have IPC (Inter Process Communication) in .NET platform?

Alan
"Richard Blewett" <ri*****@dotnetconsult.co.uk> wrote in message
news:eI**************@TK2MSFTNGP15.phx.gbl...

It depends on what degree of communication you need. If they just need
coordinate their actions you can use a named Mutex (see the System.Threading namespace).

If you need proper calling with params, etc the only out-of-the-box solution is remoting (System.Runtime.Remoting and friends).

However, a while back I wrote a wrapper round shared memory that may help
you do what you want - you can find it here (watch out for line breaks):

http://staff.develop.com/richardb/do...aredmemory.zip

HTH

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

"A.M" <no*****@online.nospam> wrote in message
news:uT****************@TK2MSFTNGP12.phx.gbl...

Hi,

What is the best way to implemet Inter Process Communication in .NET ?

I developed two programs and I want to have them talk to each other.

Thanks,
Alan

[Kevin Yu [MSFT]]

Thanks for Richard's reply.

Hi Alan,

I think in .NET framework managed classes, the only way to do inter process
communication is remoting.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Kevin Yu [MSFT]]

Hi Alan,

The following IPC mechanisms are supported by Windows:
" Clipboard
" COM
" Data Copy
" DDE
" File Mapping
" Mailslots
" Pipes
" RPC
" Windows Sockets

Some of them are also supported in .net, such as sockets. For others,
PInvoke is also OK. If you need to use pure .net technologe, you can use
remoting as well.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Tim Behrsin]

I'm successfully using Remoting using Named Pipes as Channels for IPC
between a Service and a Client. No problems here... try it yourself.

http://www.thecodeproject.com/csharp...PipesPart1.asp
http://www.codeguru.com/Csharp/Cshar...cle.php/c7259/

I prefer the latter article.

Tim

[A.M]

Thank you everyone for help.

Based on your posts I underestand that Remoting is a suggested method for
inter process communication in .Net. Therefore i am going to use remoting
rather than IPC.

Thanks again,
Alan
"A.M" <no*****@online.nospam> wrote in message
news:uT****************@TK2MSFTNGP12.phx.gbl...

Hi,

What is the best way to implemet Inter Process Communication in .NET ?

I developed two programs and I want to have them talk to each other.

Thanks,
Alan

[dr]

Thanks for the links - so from what I've read Remoting and Web Services
really are the only two options for IPC in a .NET managed environment
(including moidifying Remoting as you have done with IPC). Is that correct?
"Tim Behrsin" wrote:

I'm successfully using Remoting using Named Pipes as Channels for IPC
between a Service and a Client. No problems here... try it yourself.

http://www.thecodeproject.com/csharp...PipesPart1.asp
http://www.codeguru.com/Csharp/Cshar...cle.php/c7259/

I prefer the latter article.

Tim