Production use of SignalR for Asp.Net Core

[Jenan]

Hello,

I would like to ask about production use of SignalR. I want to use the SignalR in the production and is it possible use the latest version of SignalR for Asp.Net Core or is necessary use the version for full .NET framework?

Thank you.

[davidfowl]

1. SignalR on ASP.NET Core isn't production ready
2. It requires the latest ASP.NET Core (2.x) to function properly (which isn't released yet)
3. There's 2 versions of SignalR on our myget feed today, a deprecated one https://github.com/aspnet/SignalR-Server and this one (the one that will ship). Running the other deprecated one in production is also unsupported (though I know of people using it).
4. Some people have hacked SignalR 2.x to make to run on ASP.NET Core but it's also not supported and has lots of strange quirks.
5. The .NET Framework version required to use SignalR on ASP.NET core will be .NET Framework 4.6 since we target netstandard 1.3

[Jenan]

OK, then is it necesarry or recommended waiting for new version of Asp.Net Core 2.0 and install latest version of SignalR (Microsoft.AspNetCore.SignalR)?

[shaggygi]

Yup, I would wait until the release later this year. You can hear more about updates Tuesday at https://live.asp.net/. There will also be a session at Build 2017 in less than 2 weeks.

[Jenan]

Or is it possible and stable use the following case?
ASP.NET Core Web Application (.NET Framework) and Microsoft.ApplicationInsights.AspNetCore Version="2.0.0" - with the benefit of new project structure? Or use for now old version of Asp.Net Web application project and move the project to .NET Core in the future? I need create the SignalR app as soon as possible. :)

Thanks.

[davidfowl]

There is no supported "as soon as possible" scenario. It's not done yet. You can grab packages and deal with issues or feature gaps as you encounter them (hack it until it works), but it's use at your own risk.

[Jenan]

Is it some estimate when will be done production version? :-) Q3 2017 or later?
Thank you

[grahamehorner]

@davidfowl really looking forward to watching //build on Channel9 any hints on what sessions to watch for #SignalR, #kestrel. .netstandard 2.0 etc aka the 😎 stuff

[HelloKitty]

Does the closing of this issue signal anything significant in changes towards the project? I realize it's still unreleased, and not ready for production, but is it ready for use at all? Will their be significant API churn in the upcoming months?

[davidfowl]

but is it ready for use at all?

Sure, it works but there will be API changes, especially client side. Probably not big ones but you can expect lots of churn. As for the server side hub API, it's pretty solid and there will be tweaks. Most of the other work will be in protocol changes, missing features (like scale out) and making the product stable (scale testing, browser testing).

You can follow this issue to see a big picture of the current state #394.

[joeangry]

@davidfowl what if I've got an old SignalR 2.2.2 project which is self hosted. Will I be able to call that from SignalR Core? Or are they not compatible?

[davidfowl]

@joeangry they aren't compatible. Though I'm not 100% sure what you mean by being able to "call it from signalr core".

[joeangry]

So I've got a SignalR host in v2.2.2. Then I've got a website that uses SignalR Core. Does that make more sense?

[davidfowl]

Not really. Are you asking if the SignalR Core Client is compatible with the 2.2.2 server? It's not.