Menu

How I release a Blazor app to 8 distribution channels
📰

How I release a Blazor app to 8 distribution channels

DEV Community·Urban·6 months ago
#EH0PMCkv
#blazor#dotnet#csharp#maui#webassembly
Reading 0:00
15s threshold

OpenHabitTracker is a free, open source app for taking Markdown notes, planning tasks, and tracking habits. One codebase, 8 distribution channels. This is everything I had to figure out to ship it.

The previous articles covered why there are so many entry points and how the shared Blazor component library stays platform-agnostic. This article is about what happens after you write the code - the files you need, the gotchas that aren't documented anywhere, and what you have to do on every release.

Why 8 channels?

Each distribution channel has different requirements that forced a separate entry point:

Microsoft Store - MAUI ( net9.0-windows )

Google Play - MAUI ( net9.0-android )

Apple App Store - MAUI ( net9.0-ios )

Mac App Store - MAUI ( net9.0-maccatalyst )

Flatpak (Flathub) - Photino - MAUI has no Linux target

Snap Store - Photino

Docker Hub + GitHub Container Registry - Blazor Server

ClickOnce (Windows direct download) - WPF - for users who don't want the Store

PWA - Blazor WASM

Before your…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.