What is the easiest way to have two .net applications talk to each other?

Question

We have a .net service with simple commands (e.g. play, pause, next track). This is installed on the user's workstation with its own credentials (for example, FooServiceUser). If I want to provide users with an application that can send commands to the service, what would be the easiest way to do this? Remember that I want to send commands from only one workstation to a process running on the same workstation. The teams are very simple. Also, the application must receive status from the service. those. pause, play track 21.

Should it be easy? WCF looks complicated and redundant. Everyone at SO says a remote .net connection is bad. I do not want to install MSMQ. Every mention of sockets gets a negative result.

Answer 1

For a complete, easy-to-use solution, I would recommend WCF. It only supports memory channel protocol (ICP) for this application.

What remains is what you would call "easy." The hosting part of WCF can be done in about 5 lines of code. All client code is generated. So do you really care about the number and size of assemblies that you should use (already installed), or about the number of functions that you are going to ignore?

WCF.
, - .

Answer 2

, Remoting WCF , , , , Remoting , AppDomains . , .

, WCF, - , .

Answer 3

, Windows, , , , - .., ServiceController Class ExecuteCommand.

Answer 4

WCF , . . WCF . .

Working with a regular socket is not easy in terms of coding efforts, but is easier in terms of working while working. You have full control over each bit when the channels are open or closed and something like that.