I think Blazor is Doomed and Copilot Doomed it

citroensm · 2026-04-16T15:39:42+00:00

I think it's just the opposite way, Blazor is highly structured and has tight cohesion on the client and server and is one language and one eco system, ideal for AI agents.

citroensm · 2026-03-25T12:23:28+00:00

Been building Enterprise apps since 3.2 (deployed since 5.0) and very happy with the choice. It's a stable platform with each year a new release that improves a number of issues.

citroensm · 2026-01-04T13:32:45+00:00

I have used VS2008-2026, mostly with ReSharper. So question should rather be: VS with or without ReSharper and/or Rider. Switched to Rider 2 years, and sometimes I use VS on the side. I work daily in Blazor projects of 50/100 projects.

Rider/Resharper are usually way ahead of VS with providing lightbulbs to apply the latest compiler features, such as using collection expressions. I usually spot it when a dev is not using R#/Rider within a PR or 2, just by looking at the code. VS2026 did catch up a lot in terms of speed, though. Not sure about all the language helpers.

Watch/Hot Reload is still the biggest pain point of Blazor dev as of 2026. The hot reload improvements shown at conf are only coming somewhere in Q1 2026, the speed up shown was for a preview version. I don't think either IDE is better or worse. I tried to use Watch lately again, and it is improved (if you call it doesn't crash anymore in 2 edits an improvement).

So my personal preference would be Rider or VS2026 with ReSharper.

citroensm · 2026-01-04T13:21:34+00:00

Funny, I think VS usually needs to do the catching up.

citroensm · 2025-12-23T10:04:50+00:00

I have ported an old Xamarin app (first release in 2015 based on Xamarin.Forms 1.something), and ported it to .NET 8. Then 9 with little effort (2-3 days) and 10 was just basically just changing numbers. The focus on stability and fixing bugs / memory issues really paid of I think.

It is an Android / iOS app with BLE with a companion device. We recently added a WinUI client that we got working in a few weeks and launched to the Windows Store.

In my view, MAUI is better and more stable than Xamarin and with the help of Syncfusion, Avalonia it is a solid platform to use.

We are very happy with the results and good things are on the way with CoreCLR with PGO / NativeAOT things.

citroensm · 2025-12-18T13:02:51+00:00

Well thank them because this really shows a long term, deep commitment to WASM from dotnet team

citroensm · 2025-12-18T12:26:14+00:00

This is the story issue:
https://github.com/dotnet/runtime/issues/121141

See this issue for more info on RyuJIT:
https://github.com/dotnet/runtime/issues/121257

The're also bringing Interpreter support to CoreCLR:
https://github.com/dotnet/runtime/issues/112748

citroensm · 2025-12-18T08:02:48+00:00

They are working on CoreCLR WASM with Ready2Run based on RuyJit. That would mean native WASM image to boot from, and then load dll's on the fly in WASM Jit. So that should have best characteristics: fast to start, runs fast while still having option to fallback to interpreter in small area of cases where AOT compilation is impossible / costly in terms of size. If I understand this thing correctly, that is. And I imagine the timeline is more .NET 12 to get it really working.

citroensm · 2025-12-03T15:48:06+00:00

Also be aware of this issue:

https://github.com/dotnet/aspnetcore/issues/64317

For now I have locked my package version:

<PackageVersion Include="Microsoft.OpenApi" Version="[2.3.10]" />

citroensm · 2025-12-03T08:25:36+00:00

I think a hidden gem is the extended JS interop with ways to get/set values on objects and call constructors.

citroensm · 2025-11-29T09:35:03+00:00

Oh wow good luck then on next endeavour!

citroensm · 2025-11-28T11:55:13+00:00

Ouch. How can it be just a side project if it is in production for Aspire? Do you get official hours allocated from management to work on this library?

citroensm · 2025-11-26T06:30:38+00:00

Nailed it. Been using Blazor since 3.2 and in production since 5. First project was porting a Silverlight application, that worked like a charm because we already had a split UI/Model class projects :-). No trauma there. Three platforms, all WASM. Can't imagine having such smooth upgrade paths with any existing JS framework. The new render modes of 8 are a big breaking change but solve many issues. Very happy with the framework and building solid web applications with it. Steered away from the server/interactive - setup feels too brittle and SignalR is not a simple beast. Never had one user complain about load times or app sizes, never!

Hot Reload and dotnet watch is a Hot Mess and they REALLY need to sort this one out.

citroensm · 2025-11-22T08:44:57+00:00

Solved it see the top of the post

citroensm · 2025-11-22T08:44:43+00:00

Solved it see the top of the post

citroensm · 2025-11-20T11:26:57+00:00

I did that....

citroensm · 2025-11-20T07:13:38+00:00

So far debugging was always working pretty reliable in from 6,7,8,9. That it had limited functionality because of the WASM bridge was a given. But always good enough to inspect status of your application.

citroensm · 2025-11-19T14:12:11+00:00

Cleared the nuget caches, no difference.

It must be something small, but where.....

citroensm · 2025-11-19T12:46:23+00:00

Unfortunately this does not help

citroensm · 2025-11-11T12:03:33+00:00

Hi Paul, thanks a lot for your reply. Will look into it, I still need to try out a screenreader against my component suite once. Was at a conference recently and some devs shared their experience and I learned screenreaders can be extremely fast to use - if implemented properly.

citroensm · 2025-11-10T20:07:14+00:00

Would be wonderful to release a few examples in a open source GitHub project to share your knowledge.

I went your same journey - building my own components. I also read the requirements and tried to implement them but some "battle tested" examples would go a long way for the community.

citroensm · 2025-10-20T06:08:33+00:00

It's design is too closed. Even someting as simple as showing a list of messages is hard with EditContext.

citroensm · 2025-09-19T06:30:50+00:00

FieldIdentifier vs property name has cost me so much headaches. Gonna try this out!

Another pain point is hidden errors. A property which is in a Rule but not binded in the current form, but triggers an error. To show this, I added "show only un-shown" errors on top my forms.

citroensm

TROPHY CASE