SignalR on .NET 5: everything you need to know

Name: SignalR on .NET 5: everything you need to know
Rating: 4.3 (45 reviews)

Enabling two-way real-time communication between the client and the server on ASP.NET Core 5

Created byFiodar Sazanavets

Last updated 2/2021

English

English [Auto],

What you'll learn

SignalR on .NET 5 - a library that provides a convenient wrapper for WebSocket protocol

Course content

7 sections • 50 lectures • 1h 25m total length

Introduction2:27
SignalR on .NET 5 enables persistent two-way client–server communication using the WebSocket protocol, with broad client support for chat apps and IoT devices and easy configuration and scaling.
Transport mechanisms3:06
Explore how SignalR uses three transport mechanisms—WebSocket, service events, and long polling—to enable hub and client communication that feels like remote procedure calls.
Setting up your environment0:24
Setting up your solution3:39
Configure a .NET 5 SignalR solution by creating an ASP.NET Core web app, adding a learning hub class inheriting from hub, and mapping the hub endpoint in Startup for training.
Test yourself

Introduction to SignalR Hub3:04
Explore how the SignalR hub acts as the central server class, enabling callable methods, broadcasting to all clients, using groups, and configuring endpoints with map hub in startup.
Example of SignalR Hub0:32
SignalR Hub explained2:27
Explore how a SignalR hub routes messages to all clients, the caller, and groups, including adding and removing users from groups, and handling connected and disconnected events on the server.
An example of a strongly typed Hub0:39
Strongly typed Hub explained1:27
Discover how strongly typed hubs in SignalR replace string method names with a client interface, enabling dot followed by the method name and preventing typos in receive message calls.
SignalR Hub documentation0:05
Test yourself

Introduction to SignalR clients1:34
Explore how SignalR clients connect to hubs across dotnet, JavaScript, and Blazor, with strong typing to prevent method errors. Focus on dotnet and JavaScript clients.
Setting up JavaScript client1:27
Prepare the solution for the Signaler JavaScript client by installing the library via Visual Studio or online tools, select specific files from Microsoft/signaler/latest, and add the client code.
Example of JavaScript client1:14
JavaScript client explained6:05
Learn to build a JavaScript signalR client on a simple HTML page, wiring controls to hub methods for broadcast, self, others, and group messages, with connection setup and error logging.
Setting up .NET Client1:26
Create a basic console app to demonstrate a bare bones signaler client in dot net, set the target framework to .NET 5.0, and add the signaler client package.
Example of .NET client1:02
.NET client explained4:55
Connect to a SignalR hub using a dotnet client, choose a transport (default WebSocket), and map a receive message handler to handle and log incoming messages across multiple clients.
Preparing Blazor WebAssembly client1:51
Prepare a Blazor WebAssembly client for a .NET 5 SignalR app by adding, configuring, and referencing a Blazor client project with the proper NuGet package.
Example of Blazor WebAssembly client0:58
Blazor WebAssembly client explained3:32
Explore how a web assembly client runs in the browser using razor components and HTML, and connect to a signalr hub to broadcast messages to all clients.
Additional resources0:22
Test yourself

Why WebSockets client0:58
SignalR wraps WebSocket and other protocols, letting WebSocket clients connect to a SignalR server. Learn why to connect multiple clients, or build a client when language support is missing.
Example of .NET WebSockets client0:38
.NET WebSockets client explained3:26
Discover how a .NET console client uses SignalR to simplify WebSocket communication, perform a handshake, receive messages in byte chunks, and broadcast from a Learning Hub.
Other types of WebSockets clients0:25

Introduction0:32
Secure your SignalR hub in production by applying startup and core controller security configurations. Explore fundamental security practices to protect SignalR hubs in production.
Example of CORS configuration0:15
CORS configuration explained1:45
learn how to configure cors in a SignalR on .NET 5 app by defining origin rules, methods, and credentials, using services.AddCors in startup and applying policies to control access.
Setting up authentication4:16
Configure user authentication by scaffolding identity to create a database schema for users and roles, then enable authentication in the pipeline and run migrations to update the database.
Example of Identity authentication0:32
Identity authentication explained2:24
Explore how identity authentication and authorization in .NET 5 govern access to SignalR hubs, endpoints, and methods using [Authorize], roles, and the startup configuration.
User authentication example0:24
User authentication explained2:48
Register and log in users, enforce password rules, and configure lockout and cookies in a .NET 5 SignalR app. See how authorization attributes control access to messaging and admin actions.
Enabling messaging individual users1:43
Messaging individual users2:00
Learn how to send messages to individual users using SignalR on .NET 5 by adding authenticated users to a username-named group and sending messages to the specified user.
Further reading on web application security0:47
Test yourself

Why would you need to scale out1:17
Scale out a SignalR web app by configuring built-in features to support millions of users and persistent connections across multiple instances, using a load balancer and startup class configuration.
Introducing Redis cache1:12
Learn how Radice backplane enables SignalR on .NET 5 to share connections across multiple app instances, enabling cloud scaling and cross-instance client communication.
Setting up Redis1:40
Connecting SignalR Hub to Redis2:10
Install the SignalR Redis package, configure services with the Redis address (localhost:6380), and run the app to route SignalR calls through Redis, enabling scaling of the hub.
Multiple Hub instances4:28
Scale out by running two web apps that share the same SignalR hub, using a class library for the hub and removing authorization to simulate distributed deployment.
Example of Hub Context0:13
Hub Context explained2:49
Learn how multiple scaled-out web applications share a single SignalR hub via a backplane, and how to use IHubContext with dependency injection to send messages from outside the hub.
Setting up Azure SignalR Service0:45
Azure SignalR dependencies0:42
Add a reference to our Hubs project and install the latest Microsoft.Azure.SignalR package in Visual Studio to enable your distributed web application to use the Azure resource.
Connecting application to the SignalR Service0:37
Azure SignalR code explained2:09
Scale out a SignalR hub with Azure SignalR service using a backplane, configure services with endpoint and access key, and post requests to the service API and keep clients unchanged.
More on scaling-out SignalR0:26
Test yourself

Requirements

Be able to build basic web applications on ASP .NET Core

Description

Are you a web developer or do you write IoT software? If so, you would know that many web and IoT development projects these days require the ability to establish a persistent connection between a client and a server without having to keep sending repeated requests from the client. As you may also know, such functionality may be hard to implement.

However, if you can build your server-side application on ASP.NET Core, there is a way to make this whole process easy. There is a library called SignalR. This is what I'm going to talk about in this course. As well as doing all the heavy lifting for you, the library abstracts away all complex implementation details, so your code can be made extremely simple.

However, as you would already know, nothing in programming is simple in absolute terms. Programming is a complex activity, so even those concepts that are relatively simple require some practice and studying.

This is why I've created this course. By the end of it, you should be able to build a web application that clients will be able to establish a persistent connection with and exchange the data with in real time.

This is the second SignalR course that I have published. The previous one was about using SignalR on .NET Core 2.2. However, quite a lot has changes since then. .NET 5 has since been released and SignalR has also received several updates. So, this is an updated version of the course. The second edition.

Who this course is for:

Web developers who want to enable a persistent real-time communication between the client and the server
IoT developers who want to be able to easily coordinate their devices
Any other web developers using Microsoft programming stack

SignalR on .NET 5: everything you need to know

What you'll learn

Explore related topics

Course content

Introduction4 lectures • 10min

Setting up SignalR Hub6 lectures • 8min

Setting up SignalR clients11 lectures • 24min

Connecting a standard WebSocket client4 lectures • 5min

SignalR security11 lectures • 17min

Scaling out SignalR hub12 lectures • 18min

Wrapping up2 lectures • 2min

Requirements

Description

Who this course is for: