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

.NET to JavaScript

Calling JavaScript from .NET is pretty simple. There are two ways of doing that:

  • Global JavaScript
  • JavaScript Isolation

We will go through both ways to see what the difference is.

Global JavaScript (the old way)

One way is to make the JavaScript method we want to call accessible globally through the JavaScript window, which is kind of a bad practice since it is accessible by all scripts and could replace the functionality in other scripts (if we were to accidentally use the same names).

What we can do is, for example, to use scopes, create an object in the global space, and put our variables and methods on that object so that we lower the risk a bit at least.

Using a scope could look something like this:

window.myscope = {};
window.myscope.methodName = () => { ... }

We create an object with the name myscope. Then we declare a method on that object called methodName. In this example, there is no code in the method; this is only...