Last three or four years, all of our UI were done in Blazor server. Some are in production for more than two years.
I am not saying that there are no tradeoffs, but if you are already familiar with the dot net environment and c#, writing app in Blazor could be the right path, especially for backoffice apps.
I am just started fiddling with the latest version that automatically switch from server side to wasm without the user even noticing, and it is an awesome tech. There are still some tradeoffs, but they keep polishing the stack.
For context, I do write some react from time to time (outlooks addin) and razor pages, but I still prefer Blazor over these techs.
@TomasEkeli I help one of our customers to revamp a really old site with a new Blazor app. It’s a big intranet site and the dev are C# devs and they know ASP.NET and desktop .NET apps.
The natural path was to stay on a .NET ecosystem for them. It’s not a sexy site for consumers, they use SSO with Entra, they are running the app in Azure. We would have suggested to have another web UI tech stack but we didn’t feel they could learn it fast enough vs. Blazor.
I considered it for https://dnstools.ws/, but it was very new and not mature enough when I was rebuilding the site back in 2020 or so. Only Blazor WebAssembly was available at the time; server-side / hybrid Blazor didn’t exist yet. I ended up using React + SignalR for the frontend instead, and gRPC on the backend to communicate with the worker nodes.
I’m using it at work. We have a customer portal running with it, and are working on a client-side PWA as well for a different use case / different set of users so that it can run offline.
Anyone actually using Blazor? Always seemed like a didn’t-even-show-up to me, but I’m not a front-ender.
Last three or four years, all of our UI were done in Blazor server. Some are in production for more than two years.
I am not saying that there are no tradeoffs, but if you are already familiar with the dot net environment and c#, writing app in Blazor could be the right path, especially for backoffice apps.
I am just started fiddling with the latest version that automatically switch from server side to wasm without the user even noticing, and it is an awesome tech. There are still some tradeoffs, but they keep polishing the stack.
For context, I do write some react from time to time (outlooks addin) and razor pages, but I still prefer Blazor over these techs.
@TomasEkeli I help one of our customers to revamp a really old site with a new Blazor app. It’s a big intranet site and the dev are C# devs and they know ASP.NET and desktop .NET apps.
The natural path was to stay on a .NET ecosystem for them. It’s not a sexy site for consumers, they use SSO with Entra, they are running the app in Azure. We would have suggested to have another web UI tech stack but we didn’t feel they could learn it fast enough vs. Blazor.
I considered it for https://dnstools.ws/, but it was very new and not mature enough when I was rebuilding the site back in 2020 or so. Only Blazor WebAssembly was available at the time; server-side / hybrid Blazor didn’t exist yet. I ended up using React + SignalR for the frontend instead, and gRPC on the backend to communicate with the worker nodes.
Thank you for the tools! They’ve been useful to me a little while ago.
Cool tech, awful user experience. Got blacklisted where I work as an explicit don’t use tech (despite being a Microsoft house)
I want it to work though, have a personal project that occasionally gets updated to see if they fixed things.
User experience as in developer or website visitor? Can you share a bit more about the significant issues making it a no-go?
Client-side Blazor, or server-side Blazor?
In it’s entirety I think.
I’m using it at work. We have a customer portal running with it, and are working on a client-side PWA as well for a different use case / different set of users so that it can run offline.
🙋