Event handling between process.

[archana]

Hi all,

I want to do inter process communication in c#.

I am having one application and one dll. What i want is load that dll
at runtime. After loading that dll i want to send one event from
application which should get trapped in dll. And only after dll has
completed that event i want my application to continue with next code.
Here i also want to use shared memory between application and process.

I am new to inter process communication. If i am wrong please correct
me.

thanks in advance.

[Brian Gideon]

Hi,

Have you considered .NET Remoting yet?

Brian

On Jan 30, 7:49 am, "archana" <[e-mail]:

Hi all,

I want to do inter process communication in c#.

I am having one application and one dll. What i want is load that dll
at runtime. After loading that dll i want to send one event from
application which should get trapped in dll. And only after dll has
completed that event i want my application to continue with next code.
Here i also want to use shared memory between application and process.

I am new to inter process communication. If i am wrong please correct
me.

thanks in advance.

[Willy Denoyette [MVP]]

"archana" <tr**************@yahoo.comwrote in message
news:11**********************@p10g2000cwp.googlegr oups.com...

Hi all,

I want to do inter process communication in c#.

I am having one application and one dll. What i want is load that dll
at runtime. After loading that dll i want to send one event from
application which should get trapped in dll. And only after dll has
completed that event i want my application to continue with next code.
Here i also want to use shared memory between application and process.

I am new to inter process communication. If i am wrong please correct
me.

thanks in advance.

It's not entirely clear what you are after, a dll once loaded in a process becomes an
integral part of it, that is, dll's are no stand-alone run-time entities and they are no
means for inter-process communication.
Inter process communication is about interaction between two or more processes, these
processes can use a number of available low-level technologies like sockets , named pipes,
shared memory, RPC's, DCOM etc. as an interprocess communication path. .NET wraps most of
these technologies in the System.Remoting (V2) and WCF (V3) namespace classes.

Willy.

[archana]

Hi

thanks for your rply.

Yes i read about .net remoting but i don't want client and server
concept. as my both application and dll will be on same pc.

so can i do this without remoting.

thanks in advance,

[Willy Denoyette [MVP]]

"archana" <tr**************@yahoo.comwrote in message
news:11**********************@j27g2000cwj.googlegr oups.com...

Hi

thanks for your rply.

Yes i read about .net remoting but i don't want client and server
concept. as my both application and dll will be on same pc.

so can i do this without remoting.

No, you can't without any form of inter-process channel (sockets, pipes, shared
memory.....). As I said in another reply, a dll becomes a part of the application code and
data, both processes get their private view mapped in their own process space.
What you need is a way to call functions across process boundaries (what you call event
handling), and this is exactly what Remoting is about.

Willy.