Book Image

Mastering Blazor WebAssembly

By : Ahmad Mozaffar
3.5 (2)
Book Image

Mastering Blazor WebAssembly

3.5 (2)
By: Ahmad Mozaffar

Overview of this book

Blazor WebAssembly is a revolutionary technology in software development that enables you to develop web applications with a rich user interface using C# without JavaScript. It can be run natively in the browser and soon on mobile apps with .NET MAUI, making it a superweapon in the .NET developer’s toolbox. This capability has opened the doors for the JavaScript community to have a stable framework to build single page applications (SPAs) maintained by Microsoft and driven by the community. Mastering Blazor WebAssembly is a complete resource that teaches you everything you need to build client-side web applications using C# & .NET 7.0. Throughout this book, you’ll discover the anatomy of a Blazor WebAssembly project, along with the build, style, and structure of the components. You’ll implement forms to catch user input and collect data, as well as explore the topics of navigating between the pages in depth. The chapters will guide you through handling complex scenarios like RenderTrees, writing efficient unit tests, using variant security methods, and publishing the app to different providers, all in a practical manner. By the end of this book, you’ll have the skills necessary to build web apps with Blazor WebAssembly, along with the basics for a future in mobile development with .NET MAUI and Blazor.
Table of Contents (21 chapters)
1
Part 1: Blazor WebAssembly Essentials
5
Part 2: App Parts and Features
13
Part 3: Optimization and Deployment

How rendering happens in SPAs

What you see in any web app, in the UI, is the result of the rendering process of the HTML code that represents the page or components.

In traditional web apps, when the browser requests the page, the server either sends a full HTML page in the case of static web apps, or, in situations of apps such as ASP.NET MVC, it constructs a full HTML string after doing data and UI manipulation, and then sends it to the client. The browser takes that HTML and renders it as is.

On the other hand, in the case of SPAs, the browser initially sends a request and receives a simple HTML document alongside the JavaScript (JS) libraries, or the DLLs if the framework is Blazor. The browser renders that simple page, then the logic of the JS or .NET library starts to build HTML pieces and injects or replaces them in the UI. This all happens on the browser side through a process known as manipulating the Document Object Model (DOM).

What is the DOM?

Basically, when...