Book Image

Web Development with Blazor

By : Jimmy Engström
Book Image

Web Development with Blazor

By: Jimmy Engström

Overview of this book

Blazor is an essential tool if you want to build interactive web apps without JS, but it comes with its own learning curve. Web Development with Blazor will help you overcome most common challenges developers face when getting started with Blazor and teach you the best coding practices. You’ll start by learning how to leverage the power of Blazor and explore the full capabilities of both Blazor Server and Blazor WebAssembly. Then you’ll move on to the practical part, which is centred around a sample project – a blog engine. This is where you’ll apply all your newfound knowledge about creating Blazor Server and Blazor WebAssembly projects, the inner working of Razor syntax, and validating forms, as well as creating your own components. You’ll learn all the key concepts involved in web development with Blazor, which you’ll also be able to put into practice straight away. By showing you how all the components work together practically, this book will help you avoid some of the common roadblocks that novice Blazor developers face and inspire you to start experimenting with Blazor on your other projects. When you reach the end of this Blazor book, you'll have gained the confidence you need to create and deploy production-ready Blazor applications.
Table of Contents (20 chapters)
1
Section 1:The Basics
4
Section 2:Building an Application with Blazor
14
Section 3:Debug, Test, and Deploy

Setting up the API

It is only Blazor WebAssembly that needs access to the Web API since it does not have direct database access. The most common architecture is probably to use a Web API for Blazor Server as well.

Let's hook up our MyBlog.WebAssembly project to our API and here is where dependency injection shines.

In our Blazor Server project, we have the services.AddScoped<IMyBlogApi, MyBlogApiServerSide>(); configuration telling our app that when we ask for an instance of IMyBlogApi, Blazor should return an instance of the MyBlogApiServerSide class, which is a version of the API that has direct access to the database.

Our shared components only know the interface, and the instance that should be returned is configured per project.

In the Blazor WebAssembly project, we will instead return an instance of the Web API client we created in Chapter 7, Creating an API.

However, it doesn't make sense that the Blazor WebAssembly project references a library...