Blazor

In my Blazor projects, the business logic has been tested with xUnit for a long time, but the components themselves were not. If an @if showed the wrong button, I only saw it by opening the page. In this post, we add a bUnit test project to a Blazor application and cover the cases I run into most often.

Part 2 in the “Behind arbitres.ca” series: Part 1 – Scheduling umpires without Excel | Version française

In the first article, I introduced arbitres.ca and its stack. Here I move on to the method. At the end of July, the repository had 280 commits, 68 specs and 9 skills, built up over about two and a half months of evenings.

Part 1 in the “Behind arbitres.ca” series: Part 2 – How I built it with AI | Version française

Someone close to me umpires in minor league baseball. That’s how I saw the way associations handle their umpire assignments, often with an Excel file and a bunch of text messages. I also wanted a project big enough to really test Blazor and Supabase, and the way I work with AI.

Part 5 in the “Local AI with Ollama and .NET” series: Part 1 – Ollama and .NET | Part 2 – Local RAG | Part 3 – AI Agents | Part 3.5 – MCP Server | Part 4 – Microsoft Agent Framework | Version française

Through the rest of the series, Ollama ran by hand: installed locally on the machine, the ollama pull done manually, and the .NET app pointing at Ollama’s local address hardcoded. It works, but it’s several manual steps to repeat on every machine. Aspire takes care of this configuration. I wanted to see what it changes.