You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So .NET 8 has now arrived and it offers some possibilities for restructuring existing Blazor applications that were created using either a Server or WebAssembly approach.
It's obviously possible to just update the libraries to their .NET 8 versions without restructuring, but it's worth considering any possible benefits or drawbacks of using things like the new render modes.
Here's the Microsoft guide to updating a Server app to .NET 8:
I don't particularly like the new Blazor project templates that Microsoft have adopted for .NET 8 (with multiple projects and all razor files under a single 'components' folder), but more importantly I don't think there's a compelling reason to adopt the new render modes in this application.
It would also mean completely ripping up the current UI + API project structure.
So I'm going to close this issue, while obviously keeping an eye on future changes in .NET 9 and beyond.
So .NET 8 has now arrived and it offers some possibilities for restructuring existing Blazor applications that were created using either a Server or WebAssembly approach.
It's obviously possible to just update the libraries to their .NET 8 versions without restructuring, but it's worth considering any possible benefits or drawbacks of using things like the new render modes.
Here's the Microsoft guide to updating a Server app to .NET 8:
Update a Blazor Server app
The text was updated successfully, but these errors were encountered: