Understanding the Anatomy of a Blazor WebAssembly Project
Blazor has become a trend in the world of software development, due to its simplicity, productivity, and wide-ranging applicability in web, mobile, and desktop application development via .NET Multi-platform App UI (MAUI) (more about MAUI in Chapter 15, What’s Next?). Thus, it is beneficial for developers to learn about and master this framework.
This book will help you master Blazor WebAssembly by building a new project in Visual Studio until you have a fully functional app that is secure, robust, deployed online, and ready to be consumed by the public.
In this chapter, we are going to walk you through the basic structure of a Blazor WebAssembly standalone application. We will start by creating the project using the various methods available on different platforms, including the Visual Studio IDE, Visual Studio Code, and the .NET CLI. You will then learn about the general structure of the project and what each file contains and why it’s there. You will also learn about dependency injection (DI), how to register and inject services, and how to store and retrieve the configuration of your application in single or multiple environments.
By the end of this chapter, you will have a good idea of the structure of the application we will be building in the later chapters of this book.
In this chapter, we will cover the following topics:
- Creating your first Blazor WebAssembly project
- Discovering the project structure
- Dependency injection in Blazor WebAssembly
- Creating, storing, and retrieving the app configuration
- Managing application environments