The way ServiceStack and SignalR will be able to integrate in future will be through .NET Core’s IApplicationBuilder pipeline which by design supports running multiple frameworks within the same App that can now share the same default route namespace.
From the v4.5.2, ServiceStack now supports running on .NET Core, please see the guide in the full release notes which shows how to register ServiceStack’s AppHost in .NET Core: http://docs.servicestack.net/releases/v4.5.2.html
SignalR for .NET Core has yet to be released but it’s expected you’ll be able to access SignalR via its dependencies registered in .NET Core’s Startup which will also be injected in your Services like normal IOC dependencies.
We’ll update this feature request again with an example showing a demo of ServiceStack + SignalR together in the same App once SignalR is available on .NET Core in 2017.
Now that SignalR has officially release, https://docs.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-2.2
Do you plan on adding some examples and/or documentation on how to best integrate it into service stack. It would be awesome if the jsonclient got support for it with the backend.
Out of curiosity is there any movement on this?
Would love to see this as well considering storage accounts are more prevalent than having to setup Service Bus or Redis.
32 votesSam Bosell shared this idea ·