Command pattern with SignalR

I’m using SignalR as a long poll mechanism between multiple .NET clients because part of my projects requirements is to have everything over http/https. There’s no point in rolling my own socket based long poll since SignalR has already done all the heavy lifting. Unfortunately since the app I work on is distributed I can’t upgrade my SignalR version from what I have (0.5.2) since the newer SignalR versions aren’t backwards compatabile. This means I have to make do with what this version of SignalR gives me.

Still, the version I have works great for my purposes and I can’t complain. However, I was getting frustrated at having to constantly update my internal boilerplate whenever I wanted to add a new hub method dispatch. What I want is to have a single method dispatch and encapsulate all my business logic in a command pattern so that I never have to update my SignalR hub code. Instead I want to only need to add a new command and everything magically gets executed when someone sends a remote action using it.

The Old Way

As an example, you can (or used to, since I know SignalR has changed a lot since the version that I have), do this to create a hub proxy connection:

var Connection = new HubConnection(Url);

var Hub = Connection.CreateProxy("hubName");

Hub.On<string>("DynamicMethodCall", DynamicMethodReference);

So when the server invokes


Your client will get foo passed to the DynamicMethodReference function.

But if you start having a lot of client method calls, then this becomes a pain to update. Each time you want to dispatch a new method you have to update both your client and your server and its easy to forget to do. You may be thinking “but its just one server call and one client call, so what, who cares?“, and I agree, if you have a simple use case.

Of course nothing is ever simple, right? In my application, I have a facade hiding the actual SignalR implementation. The outside code doesn’t touch the dynamic clients object, since there is a lot of code to manage finding the right client based on a bunch of things like separate keys and who is and isn’t connected, etc.

In addition, when you work in a large application it’s always a good idea to separate out 3rd party libraries behind firewalls like that, it makes them easier to update later. The last thing you want is a spaghetti mess of 3rd party code all over your app that you can’t update easily. It’s a little more work up front but it pays off later. The downside is that to make changes to the external API you need to also update the internals. So, being able to have one single entry point and exit point makes things a lot neater in the long run. Less boilerplate means more fun times making things do stuff!


To solve this problem, I wanted to send an encapsulated object that contained my data and code to do the work I wanted. For example, what I wanted to end up with was:

var Connection = new HubConnection(Url);

var Hub = Connection.CreateProxy("hubName");

Hub.On<RemoteCommand>("RemoteCommand", RemoteCommadHandler);

Where RemoteCommand would be an abstract base class. This would let me focus on my business logic and not my interconnect logic. If I wanted to invoke an echo on a client I could do this:

public class EchoCommand : RemoteCommand
    public override void Execute(){

And to send it from the server would look like this

client.RemoteCommand(new EchoCommand());

Later, if I had something else I wanted to invoke all I’d need to do is make a new command and dispatch it on the client again.

public class LogMeCommand : RemoteCommand
    public override void Execute(){
         Log.Debug("log me happened!");
client.RemoteCommand(new LogMeCommand ());


I was hoping this would work but originally it didn’t. Obviously the fact that I had registered an abstract base class was preventing it from working.

The first thing I did was change my Hub.On code to be of type dynamic. When I did that I was able to execute the registered command, but it came back as a json type. This tipped me off that the default JSON serializer that SignalR was using didn’t serialize the inheritance structure.

To test this theory out I manually serialized json on the server side, sent a string over the wire, then deserialized the item on the client side. This worked perfectly and maintained all my inheritance structure.

Next step was to find out how to replace the JSON serializer in an old SignalR version. The SignalR dev’s theoretically made SignalR extremely extensible. They’ve exposed a dependency injection hook to register your own serializer. All they claim you had to do was add

        typeof (IJsonSerializer),
        () => JsonSerializer.Create(new JsonSerializerSettings
            TypeNameHandling = TypeNameHandling.All

In the Application_Start function of your site (or wherever your app start may be). But, this didn’t work for me. Not sure what I was doing wrong, but my endpoints that needed to serialize this base class never got hit. Other endpoints that had basic types for the hub argument worked fine.

The Solution

Eventually I settled back on my hacky way of doing it, but at least the hack is hidden in my boilerplate and I wont have to come back to it.

When sending out I do

var serializer = new JsonSerializerSettings { TypeNameHandling = TypeNameHandling.All };
var str = JsonConvert.SerializeObject(command, serializer);

And when receiving I do

Hub.On<string>("RemoteCommand", item =>
        var rcmd = JsonConvert.DeserializeObject<RemoteCommand>(
                    new JsonSerializerSettings
                        TypeNameHandling = TypeNameHandling.All

And now everything works great.

Leave a Reply

Your email address will not be published. Required fields are marked *