« Blazor » : différence entre les versions
De Banane Atomic
Aller à la navigationAller à la recherche
Aucun résumé des modifications |
|||
| Ligne 17 : | Ligne 17 : | ||
{{ListPlusMinus|type=plus|list= | {{ListPlusMinus|type=plus|list= | ||
* .NET-based web framework that uses the C# and Razor languages. | * .NET-based web framework that uses the C# and Razor languages. | ||
* easy integration of Javascript libraries with JSInterop | * easy integration of Javascript libraries with JSInterop. | ||
}} | }} | ||
{{ListPlusMinus|type=minus|list= | {{ListPlusMinus|type=minus|list= | ||
* it requires a constant connection to the server, which can be a disadvantage if the user has a weak or unreliable internet connection. | * 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. | * scaling the application can be more challenging as it requires more server resources to support many users with SignalR. | ||
}} | }} | ||
Version du 26 octobre 2023 à 20:54
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 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.
