r/Blazor • • Dec 07 '24 Take My Silver

Blazor on a big video wall using Skiasharp for high performance rendering:

Post image
558 Upvotes

For people asking if Blazor is ready for prime time, the answer is yes. Me in France standing in front of my companies software which I’m a PgM for. WASM rules.


r/Blazor • • Dec 07 '25 Diamonds are Forever WOW Thanks Bravo

I've been building production Blazor apps for years. Here's what the "Blazor vs React" debates always get wrong.

503 Upvotes

Every few weeks someone posts "should I learn Blazor or React?" and the comments are the same: "Blazor WASM is too slow," "nobody uses Blazor," "just learn React it has more jobs."

Most of these takes are outdated or just wrong. Let me set the record straight.

"Blazor is too slow"

This was valid criticism in 2020. It's 2025.

.NET 8 gave us Static SSR pages render as pure HTML. No WASM download. No SignalR. Faster than React hydration in many scenarios. You opt INTO interactivity per-component, not the other way around.

.NET 9 added WebSocket compression by default and improved reconnection handling. .NET 10 brought framework asset preloading, AOT improvements, and automatic memory pool eviction.

Hot Reload actually works now. Edit a .razor file, save, see changes. Not quite Vite-fast, but close enough that I don't notice the difference in my workflow.

"The ecosystem is too small"

MudBlazor, Radzen, Telerik, Syncfusion, Blazorise. That covers 95% of what you'll ever need.

And when you need a JS library? IJSRuntime interop is clean:

await JS.InvokeVoidAsync("Chart.bindings.init", chartElement, chartData);

I've integrated Chart.js, Leaflet, Stripe, and various payment SDKs without issue. You're not locked out of JavaScript. You just don't drown in it.

"There are no Blazor jobs"

There are tons of .NET jobs. Blazor is just the UI layer. Any company with .NET backend work is a potential Blazor shop. They just might not know it yet.

Here's the real advantage: a senior C# dev becomes productive in Blazor within a week. The component model is intuitive, the syntax is familiar Razor. Meanwhile, hiring a "React developer" often means hiring someone who learned React 3 years ago and now needs to catch up on Server Components, the new use hook, and whatever meta-framework is trending.

What actually matters that people ignore:

Shared models between API and UI. Change a property, compiler tells you everywhere it breaks. No more "I updated the API but forgot to update the TypeScript types."

Real debugging. Breakpoints, step-through, watch expressions. Set a breakpoint in your component, trace execution to the database and back. One IDE, one language.

Validation lives in one place:

public class OrderModel
{
    [Required, EmailAddress]
    public string Email { get; set; }

    [Required, MinLength(8)]
    public string Password { get; set; }
}

Use it on client. Use it on server. Use it in background jobs. Same code.

No npm supply chain anxiety. The Shai-Hulud attack this year compromised packages with 2.6 billion weekly downloads. My dotnet list package --vulnerable stays clean.

The ceremony difference is real

Two-way binding:

  • React: value={x} + onChange={e => setX(e.target.value)}

  • Blazor: @bind="x"

Form validation:

  • React: react-hook-form + zod + resolver config

  • Blazor: [Required] attribute

Data fetching:

  • React: useEffect + cleanup flag + dependency array

  • Blazor: OnInitializedAsync()

It adds up. Less boilerplate, fewer footguns.

The real decision framework:

Pick Blazor if:

  • Your team knows C#

  • You're building a long-term enterprise app

  • You need stability over yearly framework churn

  • You already have a .NET backend

  • You want one language across the entire stack

Pick React if:

  • Your team knows JS

  • You're building a startup MVP where speed-to-market is everything

  • You need the massive third-party ecosystem

  • You're going serverless/JAMstack

Stop asking strangers which framework is "better." Ask which one fits YOUR team and YOUR project.

Happy to answer specific questions from anyone actually evaluating this.


r/Blazor • • May 31 '25

Microsoft crowns Blazor as its preferred web framework for future investment

Thumbnail
devclass.com
227 Upvotes

r/Blazor • • Nov 01 '24

This sub

Post image
179 Upvotes

r/Blazor • • Feb 22 '26

I recently built an Invoicing Web App using Blazor Interactive Server and Tailwind CSS 4 in .NET 10

Thumbnail
gallery
154 Upvotes

I recently built an Invoicing Web App using Blazor Interactive Server and Tailwind CSS 4 in .NET 10

I want to share a quick demo of the app


r/Blazor • • Aug 07 '21

Check out "FindRazorSouceFile"! 👍 - After installing this package, Ctrl+Shift+F hotkey makes Blazor apps display the source .razor file name of the element under cursor. And if this VS extension is installed, the source .razor file of clicked element will be opened in Visual Studio! 🎉

153 Upvotes

r/Blazor • • Feb 10 '22

Two weeks of blazor.. I'm sold

142 Upvotes

Have been doing development since the 90s and generally have always found the mix of js, html, css and c# to be laborious.

Even react which I find to be the least annoying js framework is painful. Most of the time I would just go back to html, css and jquery to get stuff done quicker.

But blazor, wow, just doing server side blazor for two weeks and I'm making stuff with such little faff. Everything works so painlessly.

Using radzen ui components but not their ide, this is seriously impressive stuff.

Has anyone tested how well server side blazor scales when using azure signalr service? . Now I have used this there's no going back.


r/Blazor • • Feb 16 '25

I just realized I've worked on 30+ projects in the last two years using Blazor and .NET MAUI

141 Upvotes

I just realized I've worked on 30+ projects in the last two years - everything from hobby experiments to freelance client solutions - all with Blazor and .NET MAUI!
It’s amazing how these frameworks power everything I build. If you’re still on the fence, jump in. Blazor has become my go-to framework for any project now!


r/Blazor • • Feb 27 '26

These Are My Two Very Successful Blazor Projects in Production

Thumbnail
gallery
132 Upvotes

I just wanted to share two real production projects built with Blazor.

  1. Restaurant Point of Sale (POS) System – UK

I built and deployed a POS system for a shisha bar in the UK.

It has been running in production for over 1 year.

They have a large amount of real business data, daily usage, multiple staff — and zero issues.

Honestly, I was surprised they didn’t call me even once during the year to complain about anything. The only time they contacted me was a few days ago because their SSL certificate had expired.

I even asked them: “So… no system issues at all?”

They said: “No, everything is perfect.”

Stack:

•	Blazor Server (.NET 9)

•	MudBlazor + Tailwind

•	PostgreSQL

⸻

2) Transportation Management System (TMS)

This one is massive. It’s hard to list all features in one post:

•	Financial Management

•	Logistics Operations

•	Multi-warehouse management

•	Multi-currency & multi-language

•	Real-time updates

•	Advanced security

•	Comprehensive reporting

•	And much more

The company transports goods from China to Iraq (similar to DHL), and they also purchase items on behalf of their clients.

It has also been running in production for 1 year, and they’re very happy with it.

Architecture & Stack:

Backend:

•	ASP.NET Core Web API (.NET 10)

Frontend:

•	Blazor WebAssembly Standalone (AOT enabled)

•	Syncfusion + custom components + Tailwind

Database:

•	SQL Server

Mobile App:

•	React Native with Expo

Hosting:

The company owns a Windows Server 2019 machine.

Everything is hosted on IIS, behind Cloudflare.

The server is physically in Iraq, but users access the system from both China and Iraq.

That’s one of the reasons I chose Blazor WebAssembly — so the UI behaves like a static app and reduces server rendering load across regions.

⸻

Anyway, just wanted to say:

Yes — Blazor is production ready.

Happy to answer any questions.


r/Blazor • • Sep 08 '25

Vector-Based Tetris in Blazor WebAssembly with Inline SVG

Post image
132 Upvotes

This is a Tetris game I made recently using Blazor WebAssembly.

https://vagabond-k.github.io/VegrarisDemo/

Instead of using the <canvas> element, I drew the tetrominoes using SVG tags. I think using inline SVG can also be useful when building vector graphics-based components.


r/Blazor • • Feb 11 '26

My First Blazor Project

Thumbnail
gallery
124 Upvotes

I’ve been wanting to do this project a long time ago…

The idea is a combo from a website and a mobile app for game collecting management tool.

The project name is RomCrate - and it will be available for free (in English and Portuguese) for web and mobile (Still deciding between MAUI and Blazor for it)

Did a small prototype a couple months ago with MAUI… but decided last month to start all over again using Blazor for the first time - and I’m loving it. It’s so much simple and better than ASP.NET - enjoying very much not have to create thousand controllers and keep refreshing the page when adding new datas.

Here’s a overview for my project - I’ve been doing some Twitter posts and decided to share here too.

Using only custom CSS - no botstrap or Mudblazor being used.


r/Blazor • • Mar 02 '22

Using the File System Access API to generate memes - link in comments

123 Upvotes

r/Blazor • • May 21 '24

The third edition of my book Blazor book is out. All new .NET 8 content with all the new render mode stuff in there and there is a new Raccoon on the cover (two actually). Foreword by Steve Sanderson. Right now it is on sale on Amazon https://packt.link/eY9BU hope you like it =)

Post image
119 Upvotes

r/Blazor • • Jul 27 '25

UPDATE: You asked, I listened! Blazor.WhyDidYouRender now has full Blazor WASM support!

116 Upvotes

Hey r/Blazor,

Wow. I am absolutely blown away by the incredible reception and feedback on my post yesterday about Blazor.WhyDidYouRender. Thank you all so much for the support, the ideas, and for sharing in the excitement. It truly means a lot.

The #1 piece of feedback, by a long shot, was a request for Blazor WebAssembly (WASM) support. Many of you pointed out that a tool like this would be a game-changer for client-side performance tuning.

Well, you asked, and I listened!

I'm thrilled to announce that version 2.0 is now live, and its biggest feature is comprehensive, cross-platform support for the entire Blazor ecosystem.

What's New in v2.0: Full Cross-Platform Support

The library now works seamlessly across Server, WASM, and even SSR hosting models. It automatically detects the environment and configures itself, so you can use the exact same code everywhere.

EnvironmentSupportSession ManagementConsole LoggingPerformance Tracking
🖥️ Blazor Server✅ FullHttpContextServer + Browser✅ Full
🌐 Blazor WASM✅ FullBrowser StorageBrowser Only✅ Full
📄 SSR✅ FullHttpContextServer + Browser✅ Full

It "Just Works" Out of the Box

One of my main goals was to make this as easy as possible. The library's new auto-detection feature means you don't have to change your configuration between projects.

For Blazor Server / SSR:

// In Program.cs
builder.Services.AddWhyDidYouRender(config =>
{
    config.Enabled = true;
    config.Output = TrackingOutput.Both; // Logs to server AND browser console
});

app.Services.InitializeSSRServices();

For Blazor WASM:

// In Program.cs
builder.Services.AddWhyDidYouRender(config =>
{
    config.Enabled = true;
    // Automatically adapts to browser-only logging for WASM!
    config.Output = TrackingOutput.Both; 
});

await host.Services.InitializeWasmAsync(jsRuntime);

And the best part? Your components don't need to change. The same TrackedComponentBase works everywhere.

 Blazor.WhyDidYouRender.Components.TrackedComponentBase

// Your component code...

See the Output Yourself

You get the same powerful insights, now tailored to the client-side. Track render triggers, parameter changes, and performance right in your browser's dev tools.

[WhyDidYouRender] Counter re-rendered (WASM)
├─ Trigger: StateHasChanged
├─ Duration: 1.8ms
├─ Parameters: Title (unchanged)
├─ Session: wasm-abc123def
└─ Reason: Manual state change

⚠️ Breaking Changes in v2.0.0 ⚠️

To make true cross-platform support possible, I had to introduce a few breaking changes, primarily around how the services are initialized. I've written a straightforward migration guide to help you upgrade from v1.x in just a minute or two.

Check out the Migration Guide here.

Check It Out on GitHub

Here's the link to the repository where you can find the updated README, the full feature list, and all the source code:

https://github.com/mistahoward/blazor-why-did-you-render

This has been a whirlwind 24 hours, and it's been a blast. While we're not talking thousands of people pouring in thanking me for this library - I had no idea what to expect so the outpour that was received has been greatly appreciated. This is still a brand-new library, so your feedback is more valuable than ever. Please, try it out on your WASM projects, let me know what you think, and open an issue if you find any bugs or have ideas for the roadmap.

Thank you again for being such an awesome and welcoming community!

Cheers!


r/Blazor • • Sep 17 '25

Blazor, Visual Studio 2026, .NET 10 RC 1, Aspire and HOT RELOAD

115 Upvotes

Runs smoothly, keeping the page's state intact throughout a complex, real-world project! ❤️❤️❤️
Tell me about your experience!


r/Blazor • • Mar 28 '25

I Built a SaaS in Blazor and Lived to Tell the Tale

115 Upvotes

I’ve been a software engineer for over a decade — started in consulting, moved over to product, and currently working as an engineering manager.

I’ve always wanted to build something of my own, and I finally made it happen. Naturally, as a dev, my brain immediately jumped to: what shiny tech stack can I geek out on? (Disclaimer: this is 100% not where you should start when building a SaaS, but I’m assuming I’m among other techies here, so hoping this is a safe space 😅)

The conventional wisdom is: Use Next.js and Vercel. But I didn’t want to use React or Vercel. I’m a .NET guy and wanted to build with a toolset that:

  • I’m comfortable with

  • I enjoy using

  • Aligns with my day job

Don’t get me wrong — I like React/Angular/Vue. I’ve built a bunch of full-stack apps with them. But .NET and Blazor are just more fun for me.

I went with Blazor + Azure — which felt like stepping off the beaten path. There’s not a huge number of people building full products in Blazor. It’s not that the tech can’t do it — more that the resources and starter kits just aren’t there.

Still, I went for it, and over a few months I turned what started as a fun side project into a working product. It’s been a mix of frustration and joy, and I figured I’d share a few things I learned along the way:

Some Learnings & Frustrations

  • Stop making excuses. I’m married with a kid, and I used that as an excuse for years. But I eventually decided to just find the time — an hour here or there after bedtime, a blocked-out Saturday morning. It added up.

  • Interactive server mode all the way. WebAssembly is cool, but I found it wasn’t worth the extra effort for what I needed.

  • Azure Container Apps worked surprisingly well. I’m running the Blazor app and some background workers in containers. Nothing fancy, but solid.

  • Bicep has matured a lot. I automated my entire CI/CD pipeline using Bicep, and it made me way more productive than I expected.

  • MudBlazor was great for speed, but...

    • Form binding with MudForm was frustrating.

    • The validation model breaks down fast with pre-bound forms or anything even slightly dynamic.

    • I lost hours debugging weird edge cases around state and error handling. Still, the component set is solid and I’d use it again — just with lower expectations for forms.

  • Stripe was way more painful than expected.

    • A basic tiered subscription model turned into an edge-case rabbit hole.

    • Upgrade/downgrade scenarios, webhooks, status sync — not as clean as their docs suggest.

  • Cloud isn’t cheap when it’s your card on file.

    • Startup programs help massively — I used Azure’s and it brought my infra costs close to zero.

  • I shipped way too late.

    • I got lost in the weeds on features I thought were cool.

    • Should’ve launched earlier and iterated based on actual feedback.

If you’re curious, the app is an AI-powered security scanning and uptime monitoring tool I called PenZen (https://penzen.app) — happy to share a discount, just ask.

Also been packaging the codebase into a starter kit I’m dogfooding with PenZen. If you’re building with Blazor and want a head start, I put a waitlist up here: https://blazorfast.carrd.co

Happy to answer questions or swap notes with anyone building products in Blazor.

EDIT: I’ve been blown away by the feedback, kind words and ideas generated by this post. Thank you. It’s given me that much more motivation to have a real go at this. For those who’ve expressed interest in trying PenZen out, please use the coupon code BLAZOR30 for 30 % off FOREVER. There’s a risk free 7-day free trial to make sure you love it and cancel anytime. Any and all feedback welcome.


r/Blazor • • Jun 07 '25

I’m the creator of Blazorise, a UI component library for Blazor - AMA

114 Upvotes

Hey everyone,

I’m the developer behind Blazorise, a UI component library for Blazor that started as a personal side project and slowly turned into something that now powers production apps around the world.

I’ve been building and maintaining it for several years now, supporting frameworks such as Bootstrap, FluentUI, Tailwind, and Material, as well as integrating components like DataGrid, Charts, and even a Scheduler(soon to be released).

I thought it might be fun (and hopefully helpful!) to do an AMA, whether you’re curious about:

  • How to build your own component library

  • Lessons I’ve learned supporting Blazor’s evolution

  • Handling cross-framework theming in Blazor

  • Or just the general pains and joys of OSS UI work

…or want to hear what it’s like maintaining a growing Blazor library through .NET’s ups and downs — I’m happy to answer anything.

…feel free to ask me anything!


r/Blazor • • Sep 28 '22

This is my PokeDex devloped with Blazor wasm for the purpose of practicing creating applications on the .Net stack. It consumes the PokeApi. My favorite feature is the text to voice description like from the PokeDex in the old tv shows

113 Upvotes

r/Blazor • • Nov 08 '24

Three months ago I started a side project just as an excuse to learn Blazor and I 'effin LOVE it.

110 Upvotes

Making a internal website "tool suite" for my family's insurance agency has been a dream of mine for many years, and in three months, and after many late nights learning and debugging and rewriting code after work - I'm finally proud of where I'm at...

I have absolutely fallen in love with Blazor. Sorry if this is all too annoying/excited... after finishing that video it made me realize how much damn work I've actually put in to this thing. And I would have never started if it weren't for this sub... You all are rock stars.

That is all.


r/Blazor • • Jun 06 '25

Out now: The Microsoft Fluent UI Blazor library v4.12.0!

108 Upvotes

27 PRs merged and 3(!) new contributors since our last release (about 1 month ago). See the image for what this version will bring to a future #Aspire Dashboard release. All the details at https://fluentui-blazor.net/WhatsNew. An in-depth blog will come next week.

Packages are available on NuGet now: https://www.nuget.org/packages?q=Microsoft.FluentUI.AspNetCore

Oh and btw, the core v4 package download counter is now well over 1M.


r/Blazor • • Jun 26 '25

Microsoft's documentation is really starting irritating me

102 Upvotes

Edit on 2025-06-29 :

Thank you so much for your feedback!
I’ve just created this issue on GitHub with concrete suggestions to ask Microsoft to significantly improve the formatting and presentation of its documentation.
If you care about this topic, feel free to upvote this request and add any comments on GitHub. The more people who support it, the higher the chances Microsoft will take it into consideration.

I may open another issue later about how the documentation is written, but for now, I think it’s better to clearly separate content from presentation.

Thanks in advance for your massive support on GitHub—and don’t hesitate to share this around! 😉

Original message :
I am annoyed by the poor quality of Microsoft's documentation, especially on Blazor.

I may open another issue later about how the documentation is written, but for now, I think it’s better to clearly separate content from presentation.

Thanks in advance for your massive support on GitHub—and don’t hesitate to share this around! 😉

In essence, it severely lacks context, guidance, and usage advice. The large pages are often just stacks of concepts without transitions, prioritization of importance, or explanations of typical use cases.

On the surface, it's really bad:

  • Some pages are way too long. For example, the page on navigation and routing is over 7300 words long, equivalent to 35 A4 pages (I copied and pasted it into Word to count)! And the presentation is downright off-putting.

  • The titles are not numbered and the h2 and h3 levels look exactly the same, which makes reading very difficult.

  • The translation into other languages by the AI is very poor. I often have to go back to English to understand certain sentences. It seems that Microsoft's annual investment of 80 billion dollars in AI is still not enough...

Alright, a good point to finish with: recently, the table of contents is displayed on the side and no longer at the beginning of the page, so it remains visible when scrolling through the page. It's about time!

I am quite astonished that a company like Microsoft is not capable of doing better than this. For me, documentation is not a detail, but rather one of the most important elements to make a technology accessible, understandable, and encourage its adoption. If Blazor doesn't take off, the quality of its documentation won't help matters.

I am curious to know if you often refer to this documentation and what you think of its quality.


r/Blazor • • Feb 04 '26

I built Blazor Blueprint — a shadcn/ui inspired component library for Blazor (65+ components, free & open source)

100 Upvotes

Hey r/Blazor,

I've been working on this for a while and it's finally ready to share.

What is Blazor Blueprint?

A comprehensive UI component library that brings shadcn/ui design patterns to Blazor. If you've used shadcn/ui or Radix UI in React, this will look and feel familiar.

Why I built it

I love Blazor, but every time I started a new project, I struggled with UI libraries:

  • MudBlazor is great but Material Design doesn't fit every project

  • Radzen feels very enterprise-y

  • Fluent UI locks you into the Microsoft look

I wanted the modern, clean aesthetic that React devs get with shadcn/ui. So I built it for Blazor.

What's included

65+ Styled Components:

  • Form: Button, Input, Checkbox, Switch, Select, MultiSelect, DatePicker, DateRangePicker, TimePicker, ColorPicker, RichTextEditor, FileUpload, Rating

  • Layout: Card, Tabs, Accordion, Sidebar, NavigationMenu, Breadcrumb

  • Overlay: Dialog, Sheet, Drawer, Popover, Tooltip, Command (⌘K palette), ContextMenu

  • Data: DataTable (sorting, filtering, pagination, selection), Charts (6 types)

  • Feedback: Alert, Toast, Progress, Spinner

15 Headless Primitives: When you need full control over styling, use the primitives. All behavior and accessibility, zero styling opinions.

1,640+ Lucide Icons

Key features

  • No Tailwind setup required — CSS is pre-built and ships with the package

  • Theme compatible — works with existing shadcn themes from tweakcn.com

  • Dark mode — built-in, just add .dark class

  • Two-tier architecture — use styled components for speed, primitives for control

  • Accessible — keyboard navigation, ARIA attributes, focus management

Installation

Option 1: Start fresh with the template

dotnet new install BlazorBlueprint.Templates && dotnet new blazorblueprint -n MyBlazorBlueprintApp

Option 2: Add to existing project

dotnet add package BlazorBlueprint.Components

That's it. No npm, no Tailwind CLI, no build step.

Links

For AI/coding assistant users

There's an MCP server and /llms/*.txt files so your AI tools can work with these components effectively.

Would love feedback from the community. What's missing? What would make this more useful for your projects?


r/Blazor • • Apr 06 '25

Nested routers in Blazor

100 Upvotes

Most popular front end frameworks have nested routers: The ability to have controls route to other controls independently of the main router (the URL shown in the browser).

Blazor doesn't. But here's a way to implement it:
https://github.com/AlanRVA/BlazorNestedRouters

This has various advantages such as more flexible code reuse and more UI/UX design options and it solved an issue I had which otherwise would have required a fair amount of code duplication.

Hopefully this will be natively supported in the future but until then, you can try this proof of concept (for Blazor Server only at the moment).


r/Blazor • • Sep 29 '21

Drag & drop list in Blazor - minimal implementation, no js library. (code in comment)

100 Upvotes