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

Understanding authentication in Blazor WebAssembly

With the word authentication, probably the first thing that comes to your mind is the login process with a username and password. I think that’s mostly right, but the story is a bit deeper than that.

An overall general definition for authentication is validating whether the user or the system that is trying to access certain protected resources has a valid identity or not. Think of authentication as an employee trying to access a company office. The employee passes the work ID over the scanner beside the main entrance. The system then checks whether it is a valid ID and, if it is, the door opens and allows the employee in. The employee gets their work ID in the onboarding process after getting hired, so you can map the entrance validation to the login process and the issuing of the ID to the registration process in the software world.

Authentication is not only for users (actual people who open and use the app). It can...