Sprinting Solo

exo2 — .NET and Blazor

exo1's design on .NET, for clients and teams who want or already run .NET.

Status

Usable locally (v0.1.0). Not yet in the cloud and not yet used in a client project.

What it is for

The same purpose as exo1: B2B portals and business applications with organisations, roles and Danish/English. The same rules and the same example, so a client can choose a stack without choosing a different way of working.

Stack

  • Backend: .NET 10 LTS with ASP.NET Core minimal APIs
  • Data: PostgreSQL with EF Core 10, background jobs in Postgres, HybridCache with Redis/Valkey
  • Frontend: Blazor WebAssembly with MudBlazor components
  • Contract: a C# project shared by server and client
  • Login: standard OIDC, Keycloak by default
  • Tests and hosting: xUnit, bUnit and Playwright for .NET; DigitalOcean App Platform

What comes with it

  • An architecture blueprint with the same sections as exo1's
  • A running template project with login, organisations, roles, audit log, cache and background jobs
  • The same example feature as exo1, through every layer
  • Automated checks: API, component and browser tests
  • An agent layer with rules, skills and hooks
  • CI workflows and environment specs for DigitalOcean

Environments

Locally with one command, side by side with exo1. Specs for the tst-env and prd-env are written; nothing has been created in the cloud yet.

Login and roles

As exo1: identity comes from the client's login system through OIDC, roles and memberships live in the application, and the server enforces the permissions.

How a project starts

As exo1: a copy at a given version, new logo and colours, setup, first feature with add-entity, and the example is removed.

What we can show

  • Built from an empty folder: 27 automated tests and 3 browser flows green (20 November 2026).
  • The first run from a clean copy found a bug, which was fixed and tested again.

Not in place yet

  • GitHub, CI and a tst-env in the cloud.
  • Blazor WebAssembly downloads the .NET runtime on the first visit: fine for portals, not for public sites.
  • As exo1: monitoring and a security and GDPR baseline.
  • No evaluation from a real project yet.

← The exos

exo2 — .NET and Blazor — Sprinting Solo