An Introduction to Blazor Framework from Microsoft
Flexibility of Blazor
Renderers of Blazor
The component model of the Blazor is used for measuring the UI changes, but to update and display the UI different renderers can be used. These renderers are also known as hosting models. So, do not get confused if you hear the hosting models of Blazor.
Till now there are four renderers available for developing interactive UIs.
Blazor Server is the Remote Renderer which is used for web-based UIs and it is the first available renderer from Blazor.
Blazor WebAssembly is used as the WebAssembly renderer and this one is also for developing web UIs. It was released recently by Microsoft.
Blazor Electron is the Electron Renderer that is still in an experimental phase. It can be used for developing desktop-based software that can be developed for Windows, Mac, and Linux OS.
Mobile Blazor Bindings is the renderer for mobile applications for both Android and iOS. It is also currently in the experimental phase.
Benefits and Drawbacks of Blazor
It allows you to run .NET code straight to the browser.
We need to download several applications such as wasm, .NET libraries, and Mono.wasm.
Control of HTML elements works a bit poorly.
The development cycle is extremely fast
Download size is small
Code is stored on the server
It struggles in high latency situations
It requires a stable connection with the server