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

Managing API errors

APIs are the main source of headaches in the project. API calls happen through the network and the potential for failure always exists. The API could respond differently based on the status of the response, and other scenarios could occur, such as the server being down, unhandled exceptions occurring while processing the request, or authentication and authorization errors.

For all these reasons, it’s very important to handle API requests carefully. The starting point is to understand at each point what could go wrong and what the appropriate response is in each case. If you are the developer of the API, things are easier, but if you are not, the documentation should be the main source of truth.

The BooksStore API has the Swagger page that we used in previous chapters to understand the input and output of some API endpoints. We noticed that the endpoints either succeed or retrieve the 400 Bad Request status code, which means something went wrong on the...