Communication with .NET service

Question

Possible Duplicate:
GUI and windows service communication

What is the most simple local (on one machine) IPC way between a .NET GUI application and a .NET windows service? On the lowest level it should be something like named pipes or local-sockets? Is there any infrastructure for that?

Is this an existing Windows service, or one that you are creating yourself? Is it on your local domain, over the public internet, behind a firewall? Are you expecting a high volume of traffic between your app and the service (i.e. is performance a significant consideration)? — Richard Ev, Aug 17 '12 at 08:14
@Martin - so why add the complexity of using a separate service at all? — Richard Ev, Aug 17 '12 at 08:16
@RichardEv That's out of question. We need a separate service for many reasons. — Cartesius00, Aug 17 '12 at 08:17
What do you mean by 'simple'? 'Basic', 'Easy to use', ... What did you try? — Emond, Aug 17 '12 at 08:31

score 0 · Answer 1 · answered Aug 17 '12 at 08:28

I would've thought the easiest way to do it is with a web service or RPC/RMC stuff - that way all the communication is done for you. Im not sure of the details of what classes etc you should be using unfortunately. If you start using sockets you basically have to reinvent the wheel and create you're own way of communicating between the programs, the other two options basically will involve doing a little bit of config and then everything will look like method calls

Communication with .NET service

1 Answers1