I have just migrated application to .NET 5 and guess what, I stumbled across another “tiny difference with big consequences”. Tiny Difference, Big Consequences Reloaded: SignalR in .NET Core 3.1 vs. .NET 5.
In a past blog post I wrote about a surprising change I encountered during the migration of a .NET Core 2.2 application to .NET Core 3.0. I have just migrated that same application to .NET 5 and guess what, I stumbled across another “tiny difference with big consequences”.
The situation: I have a WPF desktop client that communicates with an ASP.NET Core server that in turn communicates with a small TypeScript browser application. I use Web API for accessing files and meta data, and SignalR to call remote functions.
After the migration I ran the application and things were working fine – until a certain point, where I received the following exception in a call of SignalR’s
HubConnection.InvokeCoreAsync() (actual function name replaced with “doSomething”):
Microsoft.AspNetCore.SignalR.HubException HResult=0x80131500 Message=Failed to invoke 'doSomething' due to an error on the server. Source=System.Private.CoreLib
Real-time Web Applications with SignalR in ASP.NET Core 3.1. Getting Started with SignalR in ASP.NET Core. Create ASP.NET Core MVC project for demonstration. Configure SignalR in ASP.NET Core Application.
Dependency Injection in ASP.NET Core 3.1. What is Dependency Injection? Dependency Injection in ASP.NET Core. ASP.NET Core is designed to support the dependency injection. Dependency injection in ASP.NET Core provides helps to create loosely coupled application.
Delivering .NET Core 2.1, 3.1, and .NET 5.0 updates on Windows via Microsoft Update.
.NET 5: How to enable .NET 5 runtime on console apps instead of .NET Core 3.1? In this article I show you how to select .NET 5 instead of .NET Core 3.1 without having to create a console application in .NET Core 3.1 and then change its runtime in the project properties afterwards.
Introducing New Support for .NET 5 and .NET Core 3.1. NET v14 controls for .NET Core 3.1 and .NET 5 Windows Forms do not support design-time in Visual Studio like the full- framework Spread. NET 14 Windows Forms controls.