Last post Apr 22, 2018 02:49 AM by BenHayat
Feb 04, 2018 02:32 AM|SamU|LINK
Has anyone used a SignalR alternative for an ASP.NET Core project?
I've been waiting for SignalR Core for a long time but I'm very frustrated and tired of waiting. I read Scott Hunter's latest blog post on .NET Core 2.1 and there's a hint of SignalR Core but nothing solid.
I'm aware of Socket.io but I think that means I'll need to build a node.js backend for the server side stuff. I also know about Pusher but that's a paid service and can get expensive.
Just wanted to see if there are any other alternatives coming from the .NET Core community.
Feb 05, 2018 06:23 AM|Brando ZWZ|LINK
As far as I know, the SignalR has now provide a prerelease version 1.0.0-alpha2-final.
It now could be used in the asp.net core application.
I suggest you could try to use this version, it is now work well in asp.net core.
About how to use it in asp.net core, you could refer to below article.
Feb 05, 2018 03:43 PM|SamU|LINK
Thank you for your response. I'm already using the alpha-2 for SignalR Core and as the name suggests, it's alpha!
My frustration is the slow pace and lack of communication from the SignalR team.
Feb 06, 2018 05:12 AM|Brando ZWZ|LINK
According to the asp.net roadmap, SignalR is the high-level features are planned for the ASP.NET Core 2.1 release.
Details, you could refer to below article.
So I suggest you could wait the net core2.1 release or follow the asp.net SignalR github to find if it is updated.
Feb 28, 2018 10:11 PM|redfeet|LINK
Your prayers have been heard, there are signs of progress:
It's a preview and a little more work installing it than the RTM (due somewhere this summer, is what I understood), but you can try if it out.
Hope this helps!
Mar 03, 2018 03:21 PM|SamU|LINK
Thank you! I've downloaded the update to both .NET Core and Visual Studio and testing it now.
Apr 22, 2018 01:12 AM|BenHayat|LINK
I'm in the same boat as you described. But any other route I looked into, would/could end up "me" doing more work to integrate a third party library. And this integration might actually consume more time and resources than waiting for the real to show up.
I've decided to let MSFT team build that foundation than me trying to glue pieces together.
So, once we get the first "Beta" I'll jump in, and hopefully the docs will be ready by then.
Apr 22, 2018 02:27 AM|SamU|LINK
Agreed. Also, I like keeping things as simple as possible. Too many pieces -- especially from third parties -- can unnecessarily complicate the architecture.
I'm currently using Preview 2 and it seems to be stable.
Apr 22, 2018 02:49 AM|BenHayat|LINK
Glad to hear you're having success and confidence with the Preview.
This is an important product for MSFT against other platforms. So, they will keep it up.
I'm now working on other parts of my project, like the MVC, Web API and Xamaran Native to get the essentials going. By RTM I'm ready for SignalR...
Good luck and keep us posted on your progress!