How to implement a singleton .NET component, for use by multiple processes?

Question

I would like to implement a component in .NET, and consume it in COM-aware clients via COM interop.

I would like this component to be a singleton across all processes that use it.

This thread suggests using WCF/remoting but doesn't go into much detail. Is there a good reference/example?

score 4 · Accepted Answer · answered Dec 02 '10 at 13:33

Remoting is a relic of the past and has been replaced by WCF.

You need to implement a WCF service and set the instancing mode to Single.

I suggest you expose it as a Named Pipe service and host it on Windows service. A word of caution, however, if it starts giving you problems with Named Pipe hardening, you might have to use TCP binding.

score 0 · Answer 2 · answered Dec 02 '10 at 13:41

0

Why not create a windows service that the COM component communicates with? The COM is the interface that all your users work with while the service contains the actual logic.

answered Dec 02 '10 at 13:41

jgauffin

99,844
45
235
372

Virtual -1. No way!! Come on - COM is dead :) – Aliostad Dec 02 '10 at 14:02
OP requested COM, not me. Or have I misinterpreted the question? – jgauffin Dec 02 '10 at 14:45

How to implement a singleton .NET component, for use by multiple processes?

2 Answers2