Summary
In this chapter, we discussed how Blazor was created and its underlying technologies, such as SignalR and WebAssembly. You also learned about the render tree and how the DOM gets updated to give you an understanding of how Blazor works under the hood.
We got an overview of the different technologies you can use with Blazor, such as server-side (Blazor Server), client-side (WebAssembly), desktop, and mobile (Blazor Hybrid). This overview should have helped you decide what technology to choose for your next project.
We talked about why Blazor is a good choice for .NET developers.
We looked at SSR and (according to me) the most exciting feature in .NET 8 for Blazor, what was known as Blazor United.
In the upcoming chapters, I will walk you through various scenarios to equip you with the knowledge to handle everything from upgrading an old/existing site and creating a new server-side site to creating a new WebAssembly site.
In the next chapter, we’ll get our hands dirty by configuring our development environment and creating and examining our first Blazor app.
