By Michael Washington on 1/13/2019 4:55 PM


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…

By Michael Washington on 11/12/2018 12:03 PM


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…

By Michael Washington on 11/4/2018 1:09 PM


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…

Microsoft Visual Studio is a registered trademark of Microsoft Corporation / LightSwitch is a registered trademark of Microsoft Corporation