.Exe to .Exe communication 1

[KPharm]

Does anyone have experience with methods of EXE to EXE communication, where I can pass messages from the child EXE to the parent EXE in VB.Net?

I can do something like this with events if my EXE was to spawn classes or threads (which I'm very good at writing), but from app to app is a different story. My project lead is worried about each of the sub-EXEs running in a completely separate memory space, but he has admitted to not writing a multi-threaded app before. I have written many threaded apps before in Delphi 4 and I don't think that there will be a problem, meaning, if your threads catch and handle all exceptions, etc, then each thread shouldn't have to worry about getting killed from other threads accidently.

Can anyone back me up or offer a better solution than a multithreaded app?

Thanks

 

[chiph]

You can use the socket classes in System.Net.Sockets. This is a fairly straightforward implementation of classic Berkeley sockets (like is on a zillion Unix machines). It's mostly thread-safe (if you use the shared/static members of the class only), and performs quite well on a single machine. It has the advantage of if you want to go from multi-threading to multi-processing, all you have to do is change the destination IP address for the program module you're trying to call.

Chip H.

 

[KPharm]

Thanks, Chiph, I'll look into sockets.