This is much more complicated than @mdm described ... SignalR uses a custom HttpModule that handles hubs . Unfortunately, due to the dynamic loading of modular assemblies, it is not possible to connect this HttpModule from a module without changing the Orchard kernel.
Fortunately, I managed to figure it out and make a live demo with Orchard and SignalR , playing together well! The execution of this work was rather complicated and included the exception of the HttpModule in favor of implementing a custom route. I will pull the module into the Orchard gallery after performing the necessary cleaning and publish the update here.
UPDATE:. The module is almost complete. There have been many changes to the SignalR library since I started using them that way. In addition, there is one small change in the Orchard core (session processing) that I need to click before publishing the module.
UPDATE 2: SignalR now uses Owin, so itβs much easier to connect everything. The Orchard module is available here . You can also grab the latest code from BitBucket. By the way, I highly recommend using the code from the Orchard 1.x branch to develop SignalR due to changes in database transaction processing.
source share