How to communicate between Windows Services

Question

I have 2 windows services that I created using C#.

I would like one of the services to call a function in the second windows service.

How should I do it?

EDIT:

The issue is That I have to application that running ( I don't need them to be Rather service Process is good too) but I need this 2 application to communicate, this 2 application are on the same server,

See [related post](http://stackoverflow.com/a/86286/175679) for cross-app communication. — SliverNinja - MSFT, Jan 23 '12 at 14:52
Which kind of data? How many messages? What is average message size? — sll, Jan 23 '12 at 14:53

score 5 · Answer 1 · edited May 23 '17 at 11:52

5

Sure. There are a bunch of IPC mechanisms you could use. Remoting, TCP/HTTP Listeners, etc.

Does either service provide functionality that might be useful outside of the other service?

See this thread for more ideas: IPC Mechanisms in C# - Usage and Best Practices

EDIT: As Davide Piras pointed out, if WCF is available for you to use, then consider using it. It will simplify life. The WCF configuration files are sometimes a pain to wield, but there's a nice tool for that too: http://msdn.microsoft.com/en-us/library/ms732009.aspx

edited May 23 '17 at 11:52

Community

1
1

answered Jan 23 '12 at 14:52

jglouie

12,523
6
48
65

2

Whenever possible remoting and HTTP should be avoided in favour of WCF – Davide Piras Jan 23 '12 at 14:53

score 5 · Answer 2 · edited May 23 '17 at 12:32

5

Are the services on the same box? Do you have .NET 4? Highly recommend using the fastest mode possible, memory-mapped files.

If they're on the same box, but you don't have .NET 4, or are in a homogenous Microsoft Windows network, named pipes could work. More to the point, I'd use WCF over a named pipe.

edited May 23 '17 at 12:32

Community

1
1

answered Jan 23 '12 at 14:58

Jesse C. Slicer

19,901
3
68
87

score 4 · Answer 3 · edited Nov 06 '13 at 08:19

4

I found all the other answers correct but a little too much complicated (WCF is a big deal) and not scalable (memory and named pipes will only work on the same sever). I suggest you DotNetMQ messaging system. It's easy to use and deploy and let's you communicate even between processes running on different servers.

edited Nov 06 '13 at 08:19

Kurubaran

8,696
5
43
65

answered Jan 23 '12 at 15:35

gigi

796
9
21

How to communicate between Windows Services

3 Answers3

Linked