How deeply does .NET MAUI in Action cover Blazor?

Defines the SPA approach and rendering boundary, but stops short of explaining component implementation or application setup.

Blazor

As explained in .NET MAUI in Action

Blazor is a .NET web UI framework for building interactive web user interfaces with .NET and Razor components.

Blazor is a Microsoft SPA framework for building client-side web applications with .NET instead of JavaScript or TypeScript. Its UI can be written with Razor, connecting familiar C# and .NET workflows to interactive web interfaces. section 1.5

In .NET MAUI Blazor, a web view renders the Blazor UI while the application code runs as managed .NET code. The MAUI wrapper can package the web application as an installable binary for multiple platforms and expose platform APIs through .NET abstractions. section 1.5

A .NET application can combine Blazor with:

ASP.NET Core for an API, Blazor for the web application, and .NET MAUI for mobile and desktop clients. section 1.5
A Razor class library for sharing Blazor-compatible UI across web, mobile, and desktop applications. section 1.5

How .NET MAUI in Action covers it

liveBook manning.com

Read .NET MAUI in Action on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Pro ASP.NET Core 7, Tenth EditionThe Blazor model is the programming model in which .NET components manage web user interfaces, rendering, and user interactions.

Compare how 2 books explain Blazor →

Related concepts

Razor syntaxuses · Razor syntax is a templating syntax that combines markup with embedded .NET code and directives to generate web content.
Razor componenthas part · A Razor component is a reusable user-interface unit defined with Razor markup and .NET code that can render content and handle interactions.
Blazor WebAssemblyincludes · Blazor WebAssembly is a .NET web UI hosting model that runs application components in browsers through WebAssembly.
persistent connectionused by · A persistent connection is a communication link kept open for reuse across multiple messages or operations, rather than reestablished for each exchange.

This explainer was generated by Manning's knowledge graph from the text of .NET MAUI in Action. The section links point to the parts of the book it draws on.