This NEW feature entirely CHANGES Blazor in .NET 8!

With .NET 8, we will get server-side rendering. Server-side rendering allows us to use the Blazor component model and run the application like an ASP.NET MVC or Razor Pages application.

Let me explain what that is and how it works.

With .NET 8, I can combine the Blazor component model with the advantages of server-side rendering.

The components are rendered on the server, and the HTML output is sent to the browser. This allows for a quick first-page load, a small download size, and no SignalR connection.

We can still use interactive components with .NET 8 when we need it. But we don't need to choose whether to use Blazor Server or Blazor WebAssembly for the whole application. Instead, we can choose the rendering mode for each component.

00:00 What is Server Side Rendering (SSR)?
01:34 Server Side Rendering (SSR) in Blazor .NET 8
02:18 The new Blazor Project Template
02:53 Server-side Rendering in Action
06:13 How to Explore It Yourself
06:37 Conclusion

🔥 C#/.NET Bootcamp: The Fundamentals & more (Code FRIENDS10 for 10% OFF)*

📌 .NET Developer Roadmap

📌 YouTube Playlists:

✅ SUBSCRIBE FOR MORE VIDEOS

🚀 CONNECT & SUPPORT

CREDITS

* Affiliate Link: I earn a small commission at no additional cost

[watherby]

Please continue with this channel. For some reason, I learn effortlessly when you explain

[TheYves]

Hey Claudio, great video! What happens when you increase the counter? Is this component being re-rendered on the client or on the server? As far as I know, for the latter it still requires a websocket connection, right? I would highly prefer re-rendering on the server but with normal HTTP requests instead of a websocket connection. This is the way HTMX does it, and I think this is great in many ways for less interactive websites.

[cheesypufs]

How is this different from server pre-rendering for a server backed WASM application?