blazor

This article explains another dumb issue I ran into. Suddenly - without a warning - a Blazor app running on an Azure App Service starts becoming unresponsive. And this happens without any changes by you. How do we start investigating this?

It’s that end‑of‑year ritual again — a short pause to look back at what actually happened, what broke, and what was surprisingly useful.

Oh, Blazor Static - the dazzling, lightning-fast static site generator that turns your Blazor components into HTML gold. One of the rare pieces of tech that makes me happy day after day that I'm using it for my static sites.

This article explains a quick fix to FrontMatter fields in a solution not getting populated when using BlazorStatic. I ran into it after repeatedly exporting all of my stuff from my legacy WordPress site to my in-the-works BlazorStatic site.

This week I'll be attending Cloud Technology Townhall Tallinn 2025. It's my first time in this event that's practically next door in the beautiful town of Tallinn! Although I guess the name was kind of a dead giveaway already, right?

This article explains a couple of easy fixes for an issue, where Visual Studio refuses to properly recognize the FluentUI components you might have used in your Blazor projects. Because apparently that can (kind of randomly) happen!

This article explains how to get around a weird quirk in Azure Static Web Apps local development story. Well - one of the quirks anyway. A real showstopper issue I ran into.

This article explains how to fix an annoying issue when trying to debug a Blazor WASM (WebAssembly) project. In my case, I had a Blazor WASM SWA (Static Web App), that built just fine and ran well in Azure, but refused to be debugged.

This article explains how to fix your Blazor Hybrid MAUI application (built with Blazor Webassembly, using MAUI to build & publish for multiple different platforms like Windows, Android and iOS at once) not starting up, but throwing an unexpected...

This article will take a look at a neat authorization option for Blazor WebAssembly - utilizing group memberships when defining policies.

Let's make this short and sweet. In this particular case, upgrading a Blazor WASM solution to .NET 6 broke the authentication when deployed to Azure. The same issue could probably happen to a fresh project, though.

Yikes - ever ran into this error after deploying your ASP.NET Core web application to an Azure App Service? Yeah, me too. And when it's a production deployment, and the error didn't happen in test/QA environment, that's even more fun.

Welp - this was not a fun issue to run into! While nobody in this day and age should use Internet Explorer for any normal usage (occasional legacy scenarios aside), there are still some luddites who do (or whose IT department makes them to).

Just a quick piece of documentation, as this piece of code, has changed in different versions of .NET Core 3.0 so far a few times. Need to have things like this written down somewhere! UriHelper / NavigationManager with .NET Core 3.

Blazor is a new (ish) framework for building web UIs with C#.

Welp - just ran into this one, and as I expect others to encounter the same issue, I'd better document it right away! So in Blazor, I was crafting a simple component that'd display some data in a nice way.

This post describes how to get the currently logged-in user using ASP.NET Core. This is compared with how it's done in ASP.NET Framework. Background In ASP.NET Core (and .