Stephen S. Mitchell stephensmitchell

Preserving State in Server-Side Blazor applications

Server-side Blazor is a stateful application framework. Most of the time, your users will maintain an ongoing connection to the server, and their state will be held in the server's memory in what's known as a "circuit". Examples of state held for a user's circuit include:

The UI being rendered (i.e., the hierarchy of component instances and their most recent render output)
The values of any fields and properties in component instances
Data held in DI service instances that are scoped to the circuit

Occasionally, users may experience a temporary network connection loss, after which Blazor will attempt to reconnect them to their original circuit so they can continue.

Authentication and Authorization

Authentication means determining who a particular user is. Authorization means applying rules about what they can do. Blazor contains features for handling both aspects of this.

It worth remembering how the overall goals differ between server-side Blazor and client-side Blazor:

Server-side Blazor applications run on the server. As such, correctly-implemented authorization checks are both how you determine which UI options to show (e.g., which menu entries are available to a certain user) and where you actually enforce access rules.
Client-side Blazor applications run on the client. As such, authorization is only used as a way of determining what UI options to show (e.g., which menu entries). The actual enforcement of authorization rules must be implemented on whatever backend server your application operates on, since any client-side checks can be modified or bypassed.

Authentication-enabled templates for Server-Side Blazor

Determine the expected size of the docker-desktop-data volume

Get the base image size + additional + all docker volumes using docker system df
Add raw uncompressed size for alpine (50MB), docker for your version of windows (700MB) and linux (80MB)

docker system df

Get info for the docker-desktop-data VHD

PS C:\Users\windows-admin\AppData\Local\Docker\wsl\data> Get-VHD -Path C:\Users\windows-admin\AppData\Local\Docker\wsl\data\ext4.vhdx

	<html>
	<head>
	<!-- Material Design Lite -->
	<script src="https://code.getmdl.io/1.3.0/material.min.js"></script>
	<link rel="stylesheet" href="https://code.getmdl.io/1.3.0/material.indigo-pink.min.css">
	<!-- Material Design icon font -->
	<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">
	</head>
	<body>
	<table class="mdl-data-table mdl-js-data-table mdl-data-table--selectable mdl-shadow--2dp">

	using SkiaSharp;
	using SkiaSharp.Views.Forms;
	using System;
	using System.Runtime.CompilerServices;
	using Xamarin.Forms;

	namespace Legatro.Cross.Controls
	{
	class ProjectSymbol : SKCanvasView
	{

	# http://webapps.stackexchange.com/questions/39587/view-estimated-size-of-github-repository-before-cloning
	# tested on macOS
	echo https://github.com/torvalds/linux.git \| perl -ne 'print $1 if m!([^/]+/[^/]+?)(?:\.git)?$!' \| xargs -I{} curl -s -k https://api.github.com/repos/'{}' \| grep size

	# output:
	# "size": 1746294,

	body {
	font-family: Helvetica, arial, sans-serif;
	font-size: 14px;
	line-height: 1.6;
	padding-top: 10px;
	padding-bottom: 10px;
	background-color: white;
	padding: 30px; }

	body > *:first-child {

	using namespace System.Net
	using namespace System.Threading.Tasks
	using namespace System.Management.Automation
	using namespace System.Collections.Generic

	function Test-DNSName ([String[]]$hostnames, [int]$Timeout = 3000) {
	<#
	.SYNOPSIS
	Given a list of DNS names, returns the ones that actually resolve to an actual name
	#>

	#!/usr/bin/python

	import sqlite3
	import os
	import sys
	from applescript import asrun
	from subprocess import Popen, PIPE
	import shutil
	import requests
	import json