Blazor Server Side vs Client Side Debugging

Server Side Debugging Breakpoints can be reached from within Visual Studio. Client Side Debugging Breakpoints can not be reached within Visual Studio. Need to setup Breakpoints from within browser debugger. (Shift + Alt + D) Note: For Client Side Debugging, you may need to run browser in debugger mode using command line. You will see... » read more

Debugging Blazor WebAssembly App from within Browser

Client Side Debugging Make sure the Startup Project is set to MyApp01.Client project. Not the server project. Run debugger and press Shift + Alt + D Error message will pop up saying unable to find debuggable browser tab. Copy the command line code and run in command console. A new browser will be launched in... » read more

Blazor Dependency Injection

Overview of dependency injection Dependency injection is a best-practice software development technique for ensuring classes remain loosely coupled and making unit testing easier. Registering injectable dependencies When a Blazor application runs through its start up code, one of the things it does for us is to configure a dependency injection container. The dependency injection container... » read more

Understand Dependency Injection in Blazor

Introduction The Dependency Injection is a design pattern that helps create a loosely coupled application design. It provides greater maintainability, testability, and reusability. In this pattern, the dependencies that are required to complete the task are provided from the outer world rather than created inside the class. There are various ways to inject the dependencies:... » read more

Blazor State: Browser Storage

Browser storage For transient data that the user is actively creating, a commonly used storage location is the browser’s localStorage and sessionStorage collections: localStorage is scoped to the browser’s window. If the user reloads the page or closes and re-opens the browser, the state persists. If the user opens multiple browser tabs, the state is shared across the tabs. Data... » read more

Blazor In-memory state container service

In-memory state container service Nested components typically bind data using chained bind as described in ASP.NET Core Blazor data binding. Nested and un-nested components can share access to data using a registered in-memory state container. A custom state container class can use an assignable Action to notify components in different parts of the app of state changes. In the following... » read more

Blazor State Management

Where to persist state Common locations exist for persisting state: Server-side storage URL Browser storage In-memory state container service Server-side storage For permanent data persistence that spans multiple users and devices, the app can use independent server-side storage accessed via a web API. Options include: Blob storage Key-value storage Relational database Table storage After data... » read more

Blazor REST API

https://learn-blazor.com/architecture/rest-api/ https://github.com/software-architects/learn-blazor/tree/master/samples/RestApi