event/delegate question - newbie

[mdauria]

I am familiar with using events and delegates in an application. I am
working on a new project in work where I have two applications that are
running on the same box and I need to send a little bit of data from
one of them to the other. I was thinking about using events to do this.
I would actually just be passing little bits of data. I am unfamiliar
with how (or even if I can do it) I would actually do this. Can anyone
point me to an article or some sample code somewhere that might give me
a start?

 

[Guest]

Hi,

Firstly delegates and events cannot be used for communication between two
processes (.Net applications).

There are several other ways to achieve this.
1. Using an IPC mechanism like named pipes. But unfortunately .Net do not
have managed classes for named pipes.

2. Using .Net Remoting. You can create a server object in the .Net
applciation that should receive data and create the proxy object in the .Net
application that should send data. The client and server can communicate
across processes or machines using different channels (IPC, TCP, HTTP) and
data formats (Binary and SOAP)

Resources:
A.
http://www.microsoft.com/downloads/...37-d692-4e96-b11b-948f18583d1b&displaylang=en
B. http://weblogs.asp.net/israelio/archive/2005/01/04/346180.aspx
C. http://www.c-sharpcorner.com/Network/RemotingInNETM.asp

3. You can use MSMQ through System.Messagin namespace. This can be simpler
to use but requires that MSMQ is installed on your Windows OS. MSMQ is an
Windows OS component but ensure that it is installed properly.
Resources:
A. http://msdn2.microsoft.com/en-us/library/system.messaging.messagequeue.aspx

Hope this helps.

 

[Dave Sexton]

Hi Adityanand,

There are several other ways to achieve this.
1. Using an IPC mechanism like named pipes. But unfortunately .Net do not
have managed classes for named pipes.

IpcChannel is the .NET named pipes implemenation. ChannelName corresponds to
the name of the pipe.

Choosing a Channel on MSDN:
http://msdn2.microsoft.com/en-us/library/4b3scst2.aspx

 

[Guest]

Hi Dev,

I meant that .Net do not have direct communication classes for named pipe
based IPC. Like for instance it has Socket classes.

I _did not_ mean that IPC channel in .Net remoting do not support named pipes.

Hope this clarifies my point-1 in my original reply.

 

[Dave Sexton]

Hi,

(I don't think ChannelName corresponds to the name of the pipe - I
misinterpreted.)