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

Adding static files

Blazor can use static files, such as images, CSS, and JavaScript. If we put our files in the wwwroot folder, they will automatically be exposed to the internet and accessible from the root of our site. The nice thing about Blazor is that we can do the same with a library, it is super easy to distribute static files within a library.

At work, we share components between all of our Blazor projects, and the shared library can depend on other libraries as well. We need to add a link to the static file using the _content folder.

Take a look at this example:

<link rel="stylesheet" href="_content/MyBlog.Shared/MyBlogStyle.min.css" />

The HTML link tag, rel, and href are ordinary HTML tags and attributes, but by adding the URL that starts with _content, this is telling us that the content we want to access is in another library. The name of the library (assembly name) is followed by, in this case, MyBlog.Shared, and then the file we...