Posted by Anuraj on Tuesday, May 8, 2018 Reading time :2 minutes
This post is about how to work with SignalR service in Azure. In Build 2018, Microsoft introduced SignalR in Azure as a service.
Few days back I wrote a post on how to use SignalR in ASP.NET Core. In this post I am modifying the solution to use SignalR service. So first you need to create a SignalR service. Open Azure Portal. Click on new resource, search for SignalR, and select SignalR service.
Next provide the required details. There is only two pricing tiers available, since it is for demo, I am choosing the Free tier. Use Location to specify the geographic location in which your SignalR resource is hosted. For the best performance, it is recommend that you create the resource in the same region as other components of your application. I am choosing
East Us as the location.
Next click on create. Once you created, go to the resource and look for
Settings, here you will be able to see the Connection string. You need to copy the primary connection string, which is required to configure the ASP.NET Core application.
Next you need to create the ASP.NET Core application. I am using the HelloSignalR project. You can remove the ASP.NET Core SignalR package reference from this project and you need to add the SignalR service package reference, you can do this using
dotnet add package Microsoft.Azure.SignalR -v 1.0.0-preview1-10009 command. Once it is done, open your startup.cs file, and modify
Configure methods like this.
Next you need to modify the chat.cs, which is the SignalR Hub file. This is required because in this project I was using an earlier version of ASP.NET Core. I was using
InvokeAsync method, which is changed to
Next you need to create an AppSettings.json file and add the SignalR connection in that. SignalR middleware is expecting something like this -
Now your completed all the setup, now run the application using
dotnet run command. And browse for
http://localhost:5000/index.html, you will be able to see something like this in the developer console.
SignalR service in Azure is fully-managed service allows you to use ASP.NET Core SignalR to build real-time experiences such as chat, stock tickers, live dashboards, and more, all without worrying about capacity provisioning, scaling, or persistent connections.
Happy Programming :)
What do you think? I would like to hear your thoughts, suggestions, and questions in the comments section below.