Dan Elliott DanElliott

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

Jekyll & Liquid Cheatsheet

A list of the most common functionalities in Jekyll (Liquid). You can use Jekyll with GitHub Pages, just make sure you are using the proper version.

Running

Running a local server for testing purposes:

Markdown cheatsheet

(Also see [remarkable][], the markdown parser created by the author of this cheatsheet)

	// For complete examples and data files, please go to https://github.com/aspose-pdf/Aspose.PDF-for-.NET
	// The path to the documents directory.
	string dataDir = RunExamples.GetDataDir_AsposePdf_Annotations();

	// Open document
	Document pdfDocument = new Document(dataDir + "AddAnnotation.pdf");

	// Create annotation
	TextAnnotation textAnnotation = new TextAnnotation(pdfDocument.Pages[1], new Aspose.Pdf.Rectangle(200, 400, 400, 600));
	textAnnotation.Title = "Sample Annotation Title";

	/**
	* Retrieves all the rows in the active spreadsheet that contain data and logs the
	* values for each row.
	* For more information on using the Spreadsheet API, see
	* https://developers.google.com/apps-script/service_spreadsheet
	*/
	function readRows() {
	var sheet = SpreadsheetApp.getActiveSheet();
	var rows = sheet.getDataRange();
	var numRows = rows.getNumRows();