I've developed a WPF server-hub-typed application, and a bunch of client-typed applications.
The hub app is always a single instance (using mutex), and implements named pipes.
However, I'm having problem with the clients.
The clients are applications that send data to the hub.
They need to start the hub if it is not already running.
The problem with these clients is, they are optional and portable. Hence, the user might store them in different locations on their system. I really do not wish to deploy the Hub application with every client. What's the best way for me to implement this?
Another thing, do I *have* to use Process.Start(path, args) to start my hub application?
I've attached a sample project that I've done. But there are several problems with it, which I've not figured out how to fix.
[References I've used:]
<-- This is the one that seems the most promising (single instance + IPC), but I want a bare-minimum example so I can get a better hang on things. Besides, it crashes when I click on any of the 3 Run buttons
<-- Named pipe IPC using wcf
View Complete Post