问题
Based on my understanding, the old SignalR repository is dead: there were no commits for a year (ironically, the guys who previously committed to it, now commit to Node,js), dozens of issues without response (we experienced a bug and had to downgrade to a version that's two years old).
There's a SignalR-Server repository which is a part of ASP.NET. It was supposed to be released with ASP.NET 5 (Q1 2016) but according to roadmap, it will be released later (Q3 2016). So I guess this is the repository where the actual SignalR development is going on. But the appropriate client repository is empty. So should I use the client from the old repository and a server from the new one? That's extremely confusing.
回答1:
There will be a version 3 of signalR included in ASP.NET 5. The development team aim for a release by mid-2016. See this roadmap
Update #1 (April 2018):
- SignalR 3 will be shipped with ASP.NET Core 2.1 (see ASP.NET Blog)
- ASP.NET Core 2.1 will be released
mid-year 2018(see ASP.NET Blog) - New GitHub repo
Update #2 (June 2018)
- ASP.NET Core 2.1 has been released (see ASP.NET Blog)
回答2:
Id'say alive and kicking, https://github.com/SignalR/SignalR/pulse I think you may have been looking at commits to the master branch only.
回答3:
A new version of SignalR has been released as a part of .Net Core 2.1 (30.05.2018)
来源：https://stackoverflow.com/questions/33604086/what-is-the-development-status-of-signalr-3