Skip to content

markbuckle/Blazor-Tutorial

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 

Repository files navigation

Blazor Tutorial

Blazor is a modern front-end web framework (part of the .NET platform) based on html, css, and C# to help you build websites faster. It's essentially Microsoft's version of Facebook's React. It allows for both front end and back end development using a single development stack.

Blazor Hybrid is essentially blending both web and mobile apps.

Blazor

Client-Side and Server-Side: Blazor can run on the client-side using WebAssembly (Blazor WebAssembly) or on the server-side (Blazor Server). Blazor WebAssembly allows you to run C# code directly in the browser, while Blazor Server runs on the server and uses SignalR to communicate with the client.

Single-Page Applications (SPA): Blazor is designed for building SPAs, where the application runs in the browser and interacts with the server only when necessary.

Component-Based: Blazor uses a component-based architecture, similar to frameworks like React or Angular. Components are reusable UI elements that can be nested, shared, and managed independently.

C# and .NET: Blazor allows you to write both client-side and server-side code in C#, leveraging the .NET ecosystem for libraries and tools.

ASP.NET Core

Server-Side Framework: ASP.NET Core is primarily a server-side framework for building web applications and APIs. It handles HTTP requests and responses, routing, and server-side logic.

MVC and Razor Pages: ASP.NET Core supports the Model-View-Controller (MVC) pattern and Razor Pages, which are used to build dynamic web pages with server-side rendering.

Middleware Pipeline: ASP.NET Core uses a middleware pipeline to handle HTTP requests. This allows for a modular approach to adding functionality like authentication, logging, and error handling.

Cross-Platform: ASP.NET Core is cross-platform, meaning it can run on Windows, macOS, and Linux.

Use Cases

Blazor: Ideal for building rich, interactive web applications with a lot of client-side logic. It’s a good choice if you prefer to use C# and .NET for both client and server code.

ASP.NET Core: Best suited for building robust server-side applications, APIs, and services. It’s a great choice for applications that require complex server-side logic, data processing, and integration with other systems.

In summary, Blazor is focused on client-side interactivity and SPAs, while ASP.NET Core is a versatile server-side framework for building web applications and APIs. Your choice between the two will depend on the specific needs of your project and your preference for client-side versus server-side development.

Blazor Resources

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors