Intro to Blazor in .NET 8 - SSR, Stream Rendering, Auto, and more...

In .NET 8, Blazor has become a full-featured web framework that is modular and adaptable to your needs over time. In this video, we are going to look at how Blazor works now and how to utilize Server-Side Rendered (SSR) mode, Stream Rendering, Blazor Server components, Blazor WebAssembly components, and components that transition automatically from Server to WebAssembly using Auto mode.

[OujouMon]

Already Blazor dev here, but still learning new every moment. Big thank you for Tim !! Been giving links your videos to everybody when people asks where to learn blazor. Keep up the good work.

[FrankTank]

Hi Tim, awesome tutorial. Getting into blazor now and LOVE it. The projects layout has been refined so much it is so clean, love it, no extra fluff, just what you need. Thank you so much for explaining the difference between SSR and WASM, especially the gotchas (with examples), so good to know for future projects.

[SIBUK]

Hi Tim, this is the best explanation so far about .net 8. You are far better than any other youtuber at explaining things in a way that people understand. Thank you. I would love it if you would do a tutorial on how to convert an existing .net 7 webassembly app that uses the old duende authentication over to be a .net 8 version that uses the new auth that comes with .net 8.

[arnotek]

"I was THIS close chief!!!" (I wonder is how many people get the reference?) I just completed the older Blazor course last month and unfortunately, I am outside the refund window by several weeks. Oh well. (I still plan to purchase the new Blazor course. But hey, putting these courses together is a LOT of work - especially when they are done at this level. They are well worth the money.) Ironically, I was just about to start a new Blazor project in the beginning of December. I am going to delay the start of the project until after I finish the new Blazor course. Thanks for getting this course out in a timely manner!

[JacobHarley-lvnd]

Just getting started on blazor. This is a great heads up to get me started. Nicely paced.

[XXnickles]

I like the new models they are proposing. SSR and enhanced navigation are a most welcome improvement. I am moving my web assembly project to the new model, and I am noticing way less complexity doing what makes sense in the server and using Wasm with minimal API (within the same project) for interactivity. I am even considering if I really want to use Wasm and instead go with HTMX taking advantage of the new "render anywhere" feature; that is something that I am planning to try at some point. I think what is going to be a BIG problem for most devs is get around on what happens in the client and what happens in the server, the two-project separation tried to be the approach to guide people on it, which to me was and straight forward easy to understand approach, but it seems people are getting even more confused. Great introductory video btw!

[waynehawkins]

Amazing Tim, yet another great video and you always seem to show something new (or forgotten and a reminder). And it's worth a call out to Microsoft, you guys' rock and the framework you have develop here is incredible.

One thing you said Tim in this video on the lines of something like "Blazor Web part is kind of a API". Keen to know more on this and around authentication and do we need to now use API for a Auto (server\WASM) web project? I know you said your going to do a video on Authentication in .NET 8 soon. Look forward to it.

[goverdhanjayaram]

Thank you very much for sharing this valuable knowledge !

[christiantricarico]

Great introduction. I got all the main differences with .NET 7 Blazor. It would be interesting to demonstrate how to migrate a Blazor project from .NET 7 to .NET 8. Thank you Tim.

[shootingblueyes]

Finally understand the value of dependency injection, honestly I've mostly just been doing it because of convention and style.

[guyincognito]

It's 2023 and the number of frameworks for creating "todo lists" and "+1 counters" is overwhelming!

[svierregger]

I've been following Blazor for several years and have been put off having to select brittle Signal R or bloated WASM. I was pleased to see SSR is the default in .Net 8 Blazor. - no WASM or Signal R required. Also, interactivity is accomplished using standard Javascript. Brilliant. You get the benefits of Razor Components, the performance of SSR and industry standard interactivity support. I frankly don't understand why SSR isn't the preferred approach to Blazor apps. The magic associated with WASM and SignalR comes at a significant cost, even if the cost has been lessened somewhat in .Net 8.

[NicholasStein]

I was trying to get up the default new Blazor app up and running. This episode was very helpful in getting up to speed with the new stuff, and the better component models in particular. Of course you have not talked about many of the other challenges: data storage, auth, state, APIs, etc. I am pretty excited about SSR because that means you can run the front end from a Azure Static Web Site or even from a blob storage account. I have also been looking into other ways to do the interactivity like HTMX.

[rizwansoomro]

Updated to 17.8 :D cant wait to try new blazor

[jadenmoore]

Thank you, very helpful video! Is there an appropriate way to handle the shift from server to wasm as discussed at 36:00, without losing server resources? Especially when setting up the project with "Auto" and "Global" interactivity types, where that shift is always happening?

[JibinMN]

Neat and clean explanation. Just one doubt How we going to Publish the files for release? Since there are 2 projects created if we choose Interactivity type as Auto. So when it comes to deployment / when we publish the files to IIS, do we need to publish these 2 projects separately?

[nezqwe]

Hi,
I got a question. When I start the project with IIS Express. The weather page (with streamrendering on) does not show the loading... msg before it show the data? Works fine if u start the project with https. What's the difference?

[Arverick]

Hey, how would I go about into creating one of this apps, but having a Client-side page (like the Demo one) and have it call a component available in the other project to fetch data? In a traditional MVC server side, I'd just set the Mongo client components right into the server project and have the controllers call those. I thought the server side Blazor would be able to provide that but I don't see how.

[StateHasChanged]

Great video!. In classic Blazor server, a frequently used practice was to maintain temporary user state in a Scoped state service of some kind. With static rendering, scoped dependencies only live for the life of the single page render. So that said, what mechanism do we have to store per user "session" state that can be accessed by both InteractiveServer and Static Blazor components?

[timohermans]

Loved the explanation, Tim! Great job.

Still not sure if this replaces my normal setup with razor pages, htmx and alpinejs. I think I've worked with Blazor too little to know how Blazor stacks up to plain old html/css/js websites (built with MVC or other web framework sprinkeled with some JavaScript)