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

Rendering components dynamically

This section’s heading seems interesting, but haven’t we already seen how to render dynamic stuff in the UI? Well, what’s different here is that the component itself is not dynamic, but its rendering is.

Let’s take a real-world scenario that we usually see in many advanced and big apps (Azure Portal, for example), which have a dashboard that is customizable by the user. This app offers a huge collection of widgets (each widget is a component) and the user can create their own dashboard by choosing which widgets to place on the dashboard page.

There are many solutions for such a scenario. For example, we can store the selected widget names in an array and then iterate over the array in the dashboard page, then make an if statement based on the name of the widget, and render the corresponding component. Actually, this works, but if you think about it, the need for a customizable dashboard means a massive number of widgets...