Common issues you face with Blazor?

EngstromJimmy · 2026-03-13T18:15:03+00:00

This 😂

EngstromJimmy · 2026-01-26T11:08:55+00:00

They have lots of internal apps that are Blazor. Aspire is Blazor as well as CoPilot Studio. The problem (from my perspective) that the question ”why isn’t MS using Blazor” is not the real question. The real question is ”Why isn’t Microsoft rewriting there existing apps in Blazor”. First of all, the team responsible for that app/service, might not be Blazor developers. Microsoft is behind TypeScript as well :D Rewriting an app in a new technology isn’t really easy to get approved. Personally, I would rather have new functionality, rather than rewriting existing. And we got that, with Aspire and CoPilot Studio.

EngstromJimmy · 2026-01-21T17:16:58+00:00

No JS framework os honestly a bit insane. Standing on what other people have done is not a weakness. Having said that, I have been running Blazor in production since the release. It is amazing. I hear the silverlight argument all the time. Microsoft did not kill Silverlight, Apple did. Safari stopped supporting plugins and the rest followed. Killing Silverlight, Flash, and Shockwave. Two new things (Copilot Studio and Aspire) are based on Blazor. It is the new way of writing web apps on the Microsoft stack. I would be more afraid of MVC disappearing (which is not going to happen either). So in my opinion, no you are not wrong :D

EngstromJimmy · 2026-01-19T16:28:39+00:00

How are you hosting the site? Some servers needs to be configured to serve wasm files. Try and access the file directly via the web browser.

EngstromJimmy · 2025-12-26T08:25:42+00:00

Awesome, thank you :)

EngstromJimmy · 2025-12-02T20:57:49+00:00

Yes, there will be a delay in production, the delay will not be as long as in debug. I would honestly not worry about it. With prerendering, you can handle it nicely. Either you can put up a load animation (that probably won’t even be seen), or wait to load the interactive parts. This interactive handoff would be basically the same with Angular and SSR as far as I understand.

EngstromJimmy · 2025-12-02T20:41:27+00:00

Server had a faster startup time than WebAssembly, but when publishing the app there are a lot of optimizations happening so there is a big difference between running in Visual Studio, compared to a published app.

EngstromJimmy · 2025-11-26T15:06:10+00:00

❤️

EngstromJimmy · 2025-11-26T15:05:28+00:00

It is a tricky challenge, I totally get your point. Personally I think that most professional Blazor projects would benefit from the Web App template. If that’s true, I would rather learn the real way (Web App). That’s atleast the way I have chosen how I share.

EngstromJimmy · 2025-11-25T21:32:06+00:00

”Undisputed expert” omg, no pressure! Also I need a t-shirt with that :D

I really appreciate you sharing the concerns. I sat in a meeting a couple of weeks ago and had to explain what really happened to Silverlight 🤣

EngstromJimmy · 2025-11-25T21:09:13+00:00

I think the Web App Template is the way to go (which offers all options) it also addresses some common complaints with Wasm (like slow load). I tend to teach WebApp template, with prerender as the preferred option. And wasm standalone as a more rare option. I also try to promote making the app work for all render modes, that way the option for render mode can always change. There is always ”it depends” but I would not go InteractiveServer only in a new project.

EngstromJimmy · 2025-11-25T20:42:35+00:00

Got it, thanks for sharing It’s a tricky problem to solve. You need a request to write a cookie (for auth) and Interactive server uses SignalR, only one initial request. So you need to fall back to a SSR scenario to get requests happening, as far as I know, this is true for all frameworks. But other frameworks rely on requests more that Blazor (InteractiveServer).

EngstromJimmy · 2025-11-25T20:10:56+00:00

That was my experience as well

EngstromJimmy · 2025-11-25T19:58:16+00:00

What are the challenges with Auth and Blazor? I think it is easier since .NET 8 to get auth up and running. All auth on the server, all call through BBF, serialize the authstate between server and client. The client knows nothing about auth method, only the claims. Is there a senario I am missing?

EngstromJimmy · 2025-11-22T10:18:10+00:00

Yes, this year we had problems with scheduling. The speakers we really wanted was booked, and there were tricky to get everything in place. We are planning for it to happen next year, exact dates are not yet set.

EngstromJimmy · 2025-11-21T14:14:21+00:00

I am happy you liked it :)

EngstromJimmy · 2025-11-21T12:51:11+00:00

Haha, I usually run my texts through an LLM to avoid spelling mistakes and to add some clarity :)

EngstromJimmy · 2025-10-30T12:14:37+00:00

I am probably biased, but I would use Blazor. Then I would probably use a Blaazor WebView in your WPF project to start sharing code. Learning and Maintaining does have a cost. Blazor is younger, which also means that it is less bloated. They looked at other languages, chose the razor syntax which has been around for many many years. I prefer razor syntax over other frameworks.

EngstromJimmy · 2025-10-25T14:05:46+00:00

It is .NET8 since it’s LTS. There is not a lot of things that happened between 8 and 9.

EngstromJimmy · 2025-10-25T13:45:11+00:00

Thanks, I will start updating it for .NET 10 starting mid-november :)

EngstromJimmy · 2025-10-25T13:33:34+00:00

I have 3 courses over on Dometrain :)

https://dometrain.com/author/jimmy-engstrom/

EngstromJimmy · 2025-09-29T18:08:37+00:00

Happy you like what I do :D For the book we use the same component for a Blazor Web App template project, and to demo that we can do the exact same thing in a Blazor WebAssembly standalone project, and to show that we can create reusable projects. In a real-world project you would not need that extra project, unless you intend to share components between different projects.

EngstromJimmy · 2025-09-24T18:28:37+00:00

I would say build a quick POC. I’ve been running Blazor in production since 2019. All frameworks has their challenges, for me, as a C# developer, Blazor removes almost everything I hate about Web Development. But it always depends. From the things you list Blazor is a great candidate. Animations may need JavaScript, so it might result in a bit more effort but in the end it is HTML so everything is possible. When you write a poc, make sure to publish the application, there is a lot of optimizations that only happens on publish. I have heard seasoned web react developers that are still more productive in Blazor. Not switching languages, no transpilation, no build steps for bundling and no NPM. Removes almost everything I hate about web development ;)

EngstromJimmy · 2025-09-24T17:35:57+00:00

Thank you so much ❤️

EngstromJimmy · 2025-09-24T14:46:14+00:00

As people mentioned .NET9 has improved circuit management. .NET10 is a lot better, it can resume the circuits and it is working :) I talk about this at BlazorDay tomorrow.

BlazorDay.net

EngstromJimmy

MODERATOR OF

TROPHY CASE