Force yourself to make new components, if you see a Blazor third party component, question yourself how you can make it yourself from scratch.
After you feel confident on the basics, and feel like improving your workflow or overall app feel then go for it.
There is a lot to learn regarding component life cycle, rendering tree and user-server interaction distinguishing from classic html forms or post backs.
As a long-time developer, I've noticed that Blazor doesn't have as many templates as frameworks like Next.js or React. To help out, I created a template to save us Blazor devs some setup time. You can check it out at www.blazorlaunch.io.
If there's interest, I'm happy to make more templates to help us all get started faster. Let me know what you think!
This is kind of a common issue I see when people complain about Blazor, and I think we could make a FAQ with the most frequent "issues" people post about. Here's a few that come to mind:
- Not enough libraries: Blazor basically has the whole .NET ecosystem of libraries for logic, and a decent amount of free and paid solutions for the UI like Radzen, Mudblazor, the trio of Telerik Syncfusion and DevExpress, and more.
Are there less options than the JS bases frameworks allow? Yes, but what's there covers most of the needs of a frontend developer.
Also, this is completely offset by having a very robust ecosystem and a simple down to earth package manager. I have been forced to learn and work with react for the past year and the whole node package system is unbearable, as is having a library get dropped by its maintainer and having to:
A) Stick with the last library and hopefully not becoming literally unable to upgrade in the future because of it B) Have to replace the library with another one, which will 100% work in a completely different way and thus require a decent effort to update
and that has happened to me personally in this year, while it's never happened with Blazor in the 3 to 4 years I have made websites with it.
- JS is pain: Agreeable, and the whole point of Blazor, in my opinion, is that you do not need JS. IF you really need JS outside of downloading files and generating PDFs or need to work with a specific library that is only found in javascript, then you should consider simply not using blazor, because yes, working with javascript in Blazor is awful and probably always will be. AND EVEN THEN, you could still work with JS if you are really passionate about not dropping blazor entirely. We have seen many people work hand in hand with Microsoft to deliver complex apps which have these kind of requirements and put out successfully working products.
So, what is blazor good for?
Backend developers who want or are needed to start doing some frontend CRUD applications which do not require some complex JS based library // complex DOM interactions Blazor Server specific: LAN web applications, of which there are many cases (I'm thinking hospitals, ERPs, CRMs and many other valid examples)
These are my two cents and I'd like to read what you guys think about the common "issues" people complain about Blazor, maybe compile them and put a stickied FAQ thread about it? I think it would be helpful for many firstcomers.
I have released new update for my Blazor components. I would still like to reach to early adopters and give the license for free (forever). Few people reached me out last time, and I hope to get more. Previously when I worked on Delphi components a lot of people gave me ideas such as new column types and features and I'm happy to be in open communication with my users.
If you just want to order a license, there is a 35% discount active now. If you decide to go with me I promise that I will listen to your suggestion, features and solve any problems.
Why is Blazor so fragile and near impossible to debug? I'm creating an application, but any minor change causes the Client-side to fail and no longer load, and becomes impossible to debug. It turns a 1 hour development effort into a week-long affair. About ready to kick this BS project to the curb and work in React.
I run a small web app built with Blazor WebAssembly (.NET / ASP.NET Core). A couple of months ago I was using AI to fix this anoying reloading of the screen and changed a single line in my App.razor:
@* Before (working) *@
<HeadOutlet ="new InteractiveWebAssemblyRenderMode(prerender: true)" />
<Routes ="new InteractiveWebAssemblyRenderMode(prerender: true)" />
@* After (silent SEO disaster) *@
<HeadOutlet ="new InteractiveWebAssemblyRenderMode(prerender: false)" />
<Routes u/rendermode="new InteractiveWebAssemblyRenderMode(prerender: false)" />
I knew I had this in place due to SEO and due to faster loading times. However, the Claude Sonnet 4.6 ensured me that only old SEO Crawlers need it, modern ones will be able to read my page properly without prerender. So I was too lazy at that moment to read through the docs and do a web research.
Seemed harmless. The site still worked perfectly for real users. I didn't notice anything for weeks.
What actually happened under the hood
In Blazor WASM with prerender: true, the server renders the full HTML on the first request — including everything in <head>: page titles, meta descriptions, canonical links, Open Graph tags, hreflang, etc. The client gets real HTML instantly, and then Blazor "hydrates" it client-side afterward.
With prerender: false, the server sends a near-empty shell:
<head>
<meta charset="utf-8" />
<!-- that's basically it -->
</head>
<body>
<!-- Blazor loads here, asynchronously, after the .NET WASM runtime downloads -->
</body>
All my <PageTitle>, <HeadContent>, <meta name="description">, and <link rel="canonical"> tags were rendered client-side only — injected into the DOM by Blazor after the WASM runtime finished downloading (~1–3 seconds later).
The worst part: it took 1-2 weeks to figure out the root cause
The site worked. Users saw everything correctly. No errors, no 404s. The bug was completely invisible at the application layer. At some point I noticed that all my sales stopped to then go into search console by google and see all my pages delisted.
I went through the usual SEO rabbit holes — checking robots.txt, re-submitting sitemaps, checking for duplicate content — before I eventually found the issue. A Googlebot crawl simulation in Search Console showed the <head> as essentially empty on first load.
The fix
One word: prerender: true. That's it. Back to where I started.
Recovery took about 2 months for pages to fully return to their previous positions. Google doesn't immediately trust re-submitted sitemaps after a canonical mess — it has to re-crawl, re-evaluate, and rebuild confidence in your page signals.
Lessons learned
Prerendering in Blazor WASM isn't just a performance optimization — it's an SEO requirement. If your app lives in a public-facing context with any SEO value, prerender: false is effectively telling Google your pages have no content.
<HeadOutlet>and<PageTitle>/<HeadContent>are client-side rendered. They do nothing for crawlers without SSR/prerendering. This is obvious in retrospect but easy to miss.
Canonical tag issues compound fast. Once Google decides your pages are "incorrect canonical," it can take months to rebuild trust — even after you fix the underlying issue.
Test your site the way Googlebot sees it. Use Google Search Console's URL Inspection tool → "Test Live URL" → "View Tested Page" → "HTML" tab. If your <head> is empty there, crawlers see empty too.
Any<head>change deserves an immediate Search Console spot-check. It's a 30-second sanity check that could save months of recovery.
TL;DR: Set prerender: false in Blazor WASM, Google couldn't read any meta/canonical tags, declared my pages as duplicate/incorrect canonical, deindexed most of them. Took 2 months to recover. The fix was reverting one boolean.
The feature lets users ask things like “What is Kerrigan’s worst matchup?”. The browser model converts that question into a schema-constrained query plan, and the existing application then executes the query against the real statistics.
So the AI is being used for natural-language → structured-query translation rather than as the source of the data itself.
It works with Blazor WebAssembly and Interactive Server, although with Interactive Server the text messages/replies naturally still pass over the Blazor connection. Image bytes remain browser-local.
It's very much a preview at this point (currently .NET 10/11 and dependent on browser Prompt API support), so I’d appreciate feedback — especially on the IChatClient API integration and anything that feels awkward from a Blazor perspective.
My ASP.NET Blazor implementation of the pattern "Don't Develop GUI Tests, Teach Your App To Test Itself!" (by Pablo Santos, DDJ 2014) finally led to a catchy title. Running the tests from within the server process (IIS in the original WebForms implementation) is the key difference to the usual external Selenium tests run from the VS Test Explorer.
Having in-process access to the actual WebControl (WebForms) resp. Blazor Server Component @ref instances provides the tests with (1) the framework-generated unique HTML id resp. attribute of GUI elements for Selenium and (2) the actual model object instances that the GUI is manipulating.
The latter saves the second browser round trip in an Act-Assert test (the measured Count button in the VS Blazor Server template is the one and only evidence to support the eponymous claim), the former initially has enabled functional WebForms testing with Internet Explorer COM Interop at that time. The new SpecFlow doc page gives a brief overview.
The application under test is a persistent state machine that implements an RPN calculator in all sample web frameworks: It was originally the example for my PHP contribution to "SMC, The State Machine Compiler" by Charles W. Rapp.
In this post, I have basically one question: After implementing and using "Teach Your App To Test Itself" in ASP.NET for so long (but only the WebForms ViewState architecture pattern in an in-house corporate environment), it feels so productive and natural to me that I now have the feeling: "I must have reinvented the wheel!" - but I can't find all the other wheels out there. So, where are they hiding and what's their name?
Why do you want multithreading in WASM? I would like to know about real life cases that this is really needed. I feel some people want it without understanding why they want it.
Javascript is single threaded and I don't see JS developers asking for multithreaded Javascript.
I truly hope Microsoft can FIX the stability of the Blazor WASM environment. I'm building a Blazor application on 2019, and it is failing in unchanged code with zero useful information. Once more, I have to toss my code base and start from scratch. It sucks and wastes SO MUCH TIME.
I am on Linux and am trying to get my new Blazor project working in VSCode (again). However the official C# extension doesn't support anything else than chrome or edge for the debugging. Dotnet Watch supports any browser, but it cant be used for debugging. There are no extensions that can't do both for some reason. I found many tutorials tho they are just too complex to setup for some reason and many of them are outdated.
I am more and more looking towards learning React at this point, the more i am trying to work with Blazor.
Don't get me wrong. Rider from JetBrains had also major issue with debugging Blazor apps. Rn i found that using VS + Reshaper is the recipe for most functional environment for Blazor. Unfortunately, i can't use VS on Linux.
So any ideas or should i drop Blazor entirely?
TBH: Blazor makes me almost suicidal for past month since i picked up this framework year ago and now i am finding out that all the skills i learned are useless in real world ...
This is mostly about AI, but since all my samples are in Blazor I felt it was appropriate to post it here.
I work on mostly business applications and use a lot of retrieval augmented generation however I recently discovered the power of knowledge graphs and recently wrote a blog post about it and would love to hear feedback.
Basically if you have any data schema that has related entities you can easily build a knowledge graph saved as simple in memory json, and expose that to your AI through function tool calling.
Then allow your end users to ask questions and query that data in ways unachievable without a knowledge graph. This can also be used to update and make changes to your source data.
Hi there, here is my story. I created WASM app as internal tool for my company. I choosen WASM because app is working with confidential documents so it cannot leave the company network. Later I realized I also want to protect the code (dont want to comment reasons). I was thinking to obfuscate the code but I know its still not enough. Then I was thinking to convert to blazor server but dont want to waste time with migrating whole app to server. I dont know what I want I was just wondering if anyone would have idea how to handle this. Is there any way that that WASM would be just embedded to server? Or should I ship it as .exe? Btw even with server its problem how to ship it as I dont have access to any internal server so I would be just running the server app on my PC for time being and then maybe request for access to some VM where only I have access. Dont know. Sorry I know It doesnt make sense at some point what I am asking here but maybe someone will comp up with an idea. Thanks.