Need to initiate seperate background processes using .NET Remoting for Interprocess Communication

Question

I have an abstract factory which will initiate separate processes (.NET EXE's) on demand. The abstract factory needs to initiate processes at any time and let the newly created processes be able to communicate with processes in which the abstract factory reside. This interprocess communication is going to be done at the factory that created them. These will be background processes (no GUI involved). What's the possible solution to this problem?

.NET remoting or PIPES both make the processes able to communicate after they have been initiated, but first they need to be initiated on demand and they'll execute separate standalone processes (They will be shown in task manager as well as standing process) and then after that, the interprocess communication will take place.

Answer 1

Look at the System.IO.Pipes Namespace.

Anonymous pipes are designed for parent-child interprocess communication.

There are examples provided if you follow the link.

You can also use the named Mutex Class for synchronization and the Process Class for starting child processes.