Blazor Component Render Modes [Pt 8] | Front-end Web Development with .NET for Beginners

In this episode we'll look at the different component render modes and the different ways you can make Blazor components interactive.

Learn more:

Chapters:
00:00 - Intro
00:27 - Static server-side rendering (SSR)
01:28 - Enhanced navigation and form handling
03:40 - Streaming rendering
06:42 - Add client interactivity
11:27 - Set up interactive WebAssembly rendering
17:20 - Enable interactivity everywhere

#dotnet #blazor #web #frontend #vscode

[jimvacca]

One of the best explanations of render mode. Great job!!

[huangjiawutw]

thanks for the Beginners series, short video, clear explanations

[abdulsalamelsharif]

Thank you, This is a clear explanations

[arabiceasycode]

Well explained, but Blazor behaves differently using Visual Studio, I don't know why? but using vs code in Mac it works exactly as video.

[tinpochan]

So with 4 different mode - Static Server, Interactive Server, Interactive WebAssembly, Interactive Auto, when use which? This is kind of confusing...
At the first impression I thought using Interactive Auto would be having some advantage on performance, but someone below stated it’s actually slower than InteractiveServer.

[wusswuzz]

Creating a blazor project (dotnet new blazor -int Auto) results in warnings like "Found markup element with unexpected name 'PageTitle'. If this is intended to be a component, add a @using directive for its namespace." These are fresh new projects therefore the warnings are curious. How do you resolve that?

[osman]

I wish there was client interactivity but without Signalr or WebAssembly.

[dvwannabe]

I just thought Blazor is kinda similar to React up til this point. About rendering, does this mean Blazor also act kinda like a web server that serves SSR content? I suppose React does the same in development..? But in React you usually bundle and build everything into just 1 html, CSS, and JS for production. Or you could do SSR using next.js.

But say in production using Blazor, if you want to have an interactive site do you either have to serve WebAsm stuff, html, CSS, js... by some generic server like Nginx, or you need to have Blazor running as a server where it will generate server side rendering and return the SSR HTML, which act like next.js?

Also, isn't stream rendering something handled by the backend?

[victorcates]

I understand the render modes in isolation, but put together? Do the render modes interleaf safely? When things work automagically, I'm always afraid of whether I'm about to be bitten by things stopping working and suddenly having to deal with massive complexity. Is everyone else watching this with a befuddled expression or is it just me?