ASP.NET Core Blazor
|
Blazor is a framework for building interactive client-side web UI with .NET:
|
Create rich interactive UIs using C# instead of JavaScript.
|
Share server-side and client-side app logic written in .NET.
|
Render the UI as HTML and CSS for wide browser support, including mobile browsers.
|
Integrate with modern hosting platforms, such as Docker.
|
Build hybrid desktop and mobile apps with .NET and Blazor.
|
|
Using .NET for client-side web development offers the following advantages:
|
Write code in C# instead of JavaScript.
|
Leverage the existing .NET ecosystem of .NET libraries.
|
Share app logic across server and client.
|
Benefit from .NET's performance, reliability, and security.
|
Stay productive on Windows, Linux, or macOS with a development environment, such as Visual Studio or Visual Studio Code.
|
Build on a common set of languages, frameworks, and tools that are stable, feature-rich, and easy to use.
|
|
Components
|
Blazor apps are based on components. A component in Blazor is an element of UI, such as a page, dialog, or data entry form.
|
Components are .NET C# classes built into .NET assemblies that:
|
Define flexible UI rendering logic.
|
Handle user events.
|
Can be nested and reused.
|
Can be shared and distributed as Razor class libraries or NuGet packages.
|
|
The component class is usually written in the form of a Razor markup page with a .razor file extension.
Components in Blazor are formally referred to as Razor components, informally as Blazor components.
Razor is a syntax for combining HTML markup with C# code designed for developer productivity.
Razor allows you to switch between HTML markup and C# in the same file with IntelliSense programming support in Visual Studio.
|
|
All source of information collected from learn Microsoft page.
|
No comments :
Post a Comment