« Blazor » : différence entre les versions
De Banane Atomic
Aller à la navigationAller à la recherche
Aucun résumé des modifications |
Aucun résumé des modifications |
||
| Ligne 14 : | Ligne 14 : | ||
* Ne recharge pas la page lors de modification, il faut relancer le serveur.}} | * Ne recharge pas la page lors de modification, il faut relancer le serveur.}} | ||
= [https://learn.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-7.0#blazor-server Blazor Server description] | = [https://learn.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-7.0#blazor-server 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. | Components are executed on the server. UI updates, event handling, and JavaScript calls are handled over a SignalR connection using the WebSockets protocol. | ||
Version du 26 octobre 2023 à 20:56
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)
 |
|
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.
Blazor Server Pros / Cons
- .NET-based web framework that uses the C# and Razor languages.
- easy integration of Javascript libraries with JSInterop.
- it requires a constant connection to the server, which can be a disadvantage if the user has a weak or unreliable internet connection.
- scaling the application can be more challenging as it requires more server resources to support many users with SignalR.
