What's your favorite thing about Blazor in .NET 8?
2024 ж. 5 Нау.
3 423 Рет қаралды
Today, Daniel Roth, @danroth27, tells us about his favorite new #Blazor feature in .NET 8.
See everything that's new in ASP.NET Core 8: msft.it/6056cbuqs
Today, Daniel Roth, @danroth27, tells us about his favorite new #Blazor feature in .NET 8.
See everything that's new in ASP.NET Core 8: msft.it/6056cbuqs
Blazor wasm 🥰and SSR are the only 2 options for me. Blazor server has always been a big no for me. That ui thing it does when there's no connectivity 😪
Alguien sabes cómo implementar inicio de sesión con rendermode Serverprerendered?
Why is the guidelines from MS/Blazor so weak about the reconnect debacle on more or less all platforms? Blazor feels more or less useless on mobile, since the reconnect "experience" kills an app after Tab-sleep. Yes, there are guides - but they are really fuzzy. IMHO, no one wants the default behaviour, so why isn't the reconnect/state-machine options in the create project template?!?! If this goes on, Blazor will die due to lack of faith from developers.
I think because the best practice is not low complexity. It combines 3 languages from the other isle. Flutter, NextJS, Golang into 1 framework. The reconnect part is the most complex imho, and also the concept behind multiple rendering feature.
This might be the best thing about Blazor in a future release, but not in .net 8. It's too much "unproven" black box complexity to just dive into in its first release. Maybe it will be more proven in .net 9 or 10 (if it's still even there), but not in .net 8.
We tried to move our existing MVC to Blazor as we want part of out modules to be a PWA. Also it seems easier for some usecases to use blazor. Sadly we found that net8 has many bugs which are down to the core mechanics. Routing to sub Blazor Project in MVC is no longer possible. This was just a killer after fixxing so much other stuff. Maybe net9 oder if net9 is released maybe net8 is stable to use for production