SQL-MisterMagoo recently posted a GitHub Blazor and Razor Components example that demonstrates a compelling animation. In this post we will examine how he did it…
You can properly scale your Razor Components application by connecting it to an Azure SignalR Service…
You can log users into your server side Blazor (Razor Components) application using Google authentication…
In this example, we will authenticate a person using their Microsoft Azure account (either Personal or Work/School account). While most of the code will be in the Client part of the project, the client code is running server side so we can trust that the user was not able to alter the identity that is set for them at login…
Radzen is an application builder that has been around for years. It allows developers to build Line Of Business applications much in the way Visual Studio LightSwitch does...
The primary benefit we have when using server-side Blazor is that we do not have to make web http calls from the client code to the server code. This reduces the code we need to write and eliminates many security concerns…
You can create popups in Razor Components without the need to write any JavaScript. However, when you do need to interact with JavaScript (for example to make a call in the web browser to pull in page content from another site), this article will demonstrate how it is done…
When you create a non-server-side Blazor application you can use a method such as JWT Authentication with Dotnet Core 2.1 and Blazor app. However, server-side Blazor provides options for deeper integration between the ‘client side’ and ‘server side’ code because the ‘client side’ code is processed server-side. With server-side Blazor, we end up using less code, and things are a lot less complex because we can trust that the end-user was not able to alter or hack the ‘client side’ code…