Blazor

Liens

• Introduction to ASP.NET Core Blazor
• How to implement JavaScript Interop in Blazor
• How to create an application using Blazor and Entity Framework Core
• ASP.NET Core Blazor CRUD using Entity Framework and Web API

Description

• Développement frontend avec C#
• Intégration des bibliothèques .NET existantes (nuget)

Pas de debug avec VScode Ne recharge pas la page lors de modification, il faut relancer le serveur.

Hosting models

Hosting model	Description
Blazor Server	run components server-side. UI updates, event handling, and JavaScript calls are handled over a SignalR connection using the WebSockets protocol.
Blazor WebAssembly	runs components client-side in the browser on a WebAssembly.
Blazor Hybrid	native client (MAUI, WPF) which renders web UI to an embedded Web View control.

Blazor Server description

Components are executed on the server. UI updates, event handling, and JavaScript calls are handled over a SignalR connection using the WebSockets protocol.
On the client, the Blazor script establishes the SignalR connection with the server.
The state on the server associated with each connected client is called a circuit.
Circuits aren't tied to a specific network connection and can tolerate temporary network interruptions and attempts by the client to reconnect to the server when the connection is lost.

Blazor Server Pros / Cons

• .NET-based web framework that uses the C# and Razor languages.
• easy integration of Javascript libraries with JSInterop.

• Performances: every client actions are routed to the server and will be delayed by the network latency and will use bandwidth.
• Reduced scalability: with SignalR there is a limit to how many simultaneous connections can be handled from the clients.