You can use the Themes of .NET Tool (themesof.net) to identify roadmaps and progress on various .NET releases.
Full stack web in .NET 8 with Blazor | OD116
#MSBuild
Learn how ASP.NET Blazor in .NET 8 allows you to use a single powerful component model to handle all of your web UI needs, including server-side rendering, client-side rendering, streaming rendering, progressive enhancement, and much more!
Experiments with the new WASI workload in .NET 8 Preview 4
.NET 8 adds a new "wasi-experimental" workload, replacing the earlier Wasi.Sdk. This is a step towards giving .NET native, built-in support for server-side WebAssembly scenarios.
This video shows how to get started, then demonstrates how .NET+WASI creates possibilities for new kinds of apps and new ways to use .NET.
.NET 8 is shaping up to be a significant release for Blazor, and there’s one big reason why.
ASP.NET Core apps with native AOT have a smaller footprint, lightning-fast startup, and use less memory.
The "Blazor United" effort is really a collection of features we're adding to Blazor so that you can get the best of server & client based web development. These features include: Server-side rendering, streaming rendering, enhanced navigations & form handling, add client interactivity per page or component, and determining the client render mode at runtime. We've started delivering server-side rendering support for Blazor with .NET 8 Preview 3, which is now available to try out. We plan to deliver the remaining features in upcoming previews. We hope to deliver them all for .NET 8, but we'll see how far we get.
Preview 3 of .NET 8 includes a new project templates to create an API with a TODO service instead of the weather forecast . Looking into the generated code of this template, there are a lot more changes going on such as a slim builder and using a JSON source generator which helps when using AOT to create native .NET binaries. This article looks into the changes coming.
As with every .NET release, Microsoft improves the performance of the runtime and guess what: This release is no exception to this. In this blog post, I want to go through some of the improvements made so far (.NET 8 preview 3).
Here’s a summary of what’s new in this preview release:
- ASP.NET Core support for native AOT
- Server-side rendering with Blazor
- Render Razor components outside of ASP.NET Core
- Sections support in Blazor
- Monitor Blazor Server circuit activity
- SIMD enabled by default for Blazor WebAssembly apps
- Request timeouts
- Short circuit routes
Blazor United - Solving Blazor's biggest challenges?
