Comments on: C# – Completely Managed Inter-process Communication

By: Evan Hilb

Evan Hilb — Sat, 05 Nov 2011 21:37:37 +0000

Fantastically entertaining thank you, I do think your close audience would probably want a good deal more content familiar to this maintain the great hard work.

By: club penguin

club penguin — Tue, 23 Aug 2011 00:12:46 +0000

to the comment poster above, you are absolutely right

By: cam

cam — Wed, 29 Jun 2011 18:34:58 +0000

Just want to say your article is as astounding. The clearness in your submit is just spectacular and i could assume you’re an expert in this subject. Well together with your permission let me to clutch your RSS feed to stay updated with approaching post. Thank you 1,000,000 and please carry on the rewarding work.

By: Jacinta Marcin

Jacinta Marcin — Thu, 31 Mar 2011 23:21:49 +0000

Pretty component to content. I simply stumbled upon your web site and in accession capital to assert that I get in fact enjoyed account your weblog posts. Any way I will be subscribing on your augment or even I achievement you get admission to consistently quickly.

By: chris

chris — Sun, 27 Mar 2011 22:15:54 +0000

You made some respectable points there. I regarded on the internet for the difficulty and located most people will go together with together with your website.

By: Ryan Alford

Ryan Alford — Tue, 17 Nov 2009 14:39:11 +0000

Yes, it could be switched. If the background app was to be deemed the “Server”, then the “server” code would have to be run on another thread, just as the “client” code is ran.

Though it could cause a pause in the main app if the roles were switched. The “Connect” method that I run from the background app will pause the thread until it gets a connection to the “server”, or until the timeout has expired. I set it to 10 seconds, which would not be a good value for a main UI thread to pause for 10 seconds. However, in the background app, that 10 seconds doesn’t matter because the user never sees it.

As for the service not running, I have code that determines if it’s running or not, and starts it if it’s not running.

So I would say that either way, it should work fine.

By: Dennis

Dennis — Tue, 17 Nov 2009 08:58:38 +0000

Wouldn’t it be better to have the background-application act as the pipe-server, waiting for connections (using PipeDirection.In) and have the client activly create the connection?

In your example, I get the feeling that if the service is not running (for some reason), the application will wait forever before it can continue.

By: Ryan Alford

Ryan Alford — Mon, 28 Sep 2009 13:30:51 +0000

The full code isn’t posted there. For the communication between the applications, this is all of the code.

I am unfamiliar with a “message window” so I wouldn’t know if they are similar.

By: Ikonmx

Ikonmx — Fri, 25 Sep 2009 04:40:30 +0000

In which part of dream in code is this code posted? Would like to see the full code. Do this code work like a message window?

Best regards.