Now upgraded for .NET core 3.2.0 preview 2 - please ensure you have installed the latest Blazor templates and VS 2019 preview.
This application demonstrates the use of SignalR to create a Blazor chat application.
The SignalR client now works with Blazor WASM - so we can drop the
JavaScript client at last. The app now uses the
Microsoft.AspNetCore.SignalR.Client library which is now compatible
with the Mono WASM runtime. This really simplifies the ChatClient code.
The disconnect bug in the mono implementation of WebSockets has now been fixed. When a client disconnects it correctly disposes and the event reflects in the other clients ("xxxx has left the chat").
If you want to see how the JavaScript client version worked, I've retained it in this branch
The .NET Client is much simpler to use as it no longer needs to use JSinterop and have a JS Client code to handle the interface to SignalR.
As well as removing JavaScript, I've refactored the client and hub code, moving both of
these to a BlazorChatSample.Shared project.
A demo application is available at https://blazorchatsample.azurewebsites.net
If you have any improvements or suggestions please submit as issues/pull requests on the Github repo.
Thanks to Code-Boxx for the article https://code-boxx.com/responsive-css-speech-bubbles/ that helped me create simple CSS speech bubbles that improve the layout.