Welcome to today’s post. In today’s post I will be explaining what a Blazor Hosted WebAssembly application is, how it compares to other Blazor application hosted options, and how we can implement a basic hosted WebAssembly application using Visual Studio. In a previous post I explained what a Blazor Server application was and how to implement them. I later explained what a Blazor WebAssembly application was and how to implement them. I will explain what a Hosted Blazor WebAssembly application is in the next section. (adsbygoogle = window.adsbygoogle || []).push({}); What is a Hosted Blazor WebAssembly Application? A Hosted Blazor WebAssembly application takes the best features of a Blazor WebAssembly application and a Blazor Server application and combines them to give developers additional flexibility in accessing both client and server-side resources, which has the benefit of keeping the code more concise and promote more reusability across the components within the application. A hosted Blazor WebAssembly application is a web application that includes the components of a Blazor WebAssembly application (the client), a Blazor Server application (the server), and a common, shared library that is accessible from both the client and server sides of the application. Recall that with a Blazor WebAssembly client application, to be able to access any server-side functionality (such as a service library) or data (such as SQL data through an ORM provider such as Entity Framework Core) would require us to call an HTTP web API service from within the client application. If we wanted to access many server-side methods, functions or even data from the client WebAssembly application that resides on the browser, our application implementation size in terms of code would be quite large. The Hosted WebAssembly application architecture supports a more efficient way for Razor components within a WebAssembly to access server-side functionali