AppState Revisited in .NET 8: Carl Franklin's Blazor Train Ep 15

Carl revisits AppState in Blazor for .NET 8 with demos for Server, WebAssembly, and Auto render mode.

🚀 Get Started Today – Free 30 Day Trial 🚀

✅ Pricing and Online Demos ✅

🆘 We Are Here to Help 🆘

👍 Follow DevExpress on Social Media 👍

🏁 Review Customer Testimonials 🏁

#DevExpress #devexpress_blazor #devexpress_web #aspnet #aspnetcore #blazor #datavirtualization #blazortraining #carlfranklin #blazortrain

[DeBuie]

Great Carl! An all-in-one solution! Love it!

[hafenauer]

Your videos are amazing. Thank you for sharing your knowledge!

[BarriDuty]

this is gold, thank you very much !!!

[TimTankkanaga]

Been wondering how to do this. Thank you!

[MarcScheuner]

Carl - instead of having a separate interface IAppState (and a class implementing it) - couldn't we just exclude those properties we don't want to save with [JsonIgnore] and serialize the CascadingAppState class like that?

[blackpaw]

Nice! Clean and easy to implement.

Would the CascadingAppState be suitable for storing api tokens (such as JWT) for use with external API calls?

[Jorgearananeyra]

Hi Carl, i try to use your solution for AppState, but after i added como components and run the app, the pages are completely in blank. The solution was to delete the <CascadingAppState> in routes. why this can occur?

[tonybasallo]

Carl, it seems that registered callbacks are not de-registered/removed and will get called even after components are disposed. I thought that's what the "dangling references" catch was for, but it seems not.

[timtankka]

Carl - I am seriously trying to implement this on server side Blazor. The app runs as expected in my development environment, but does not work when published to IIS. Any ideas on how to correct this?

[CodingHaribo]

Whenever I see a try..catch without anything in the catch, that tells me something has gone wrong.

[milciadesmarrocchi]

Hi Carl, on the server example, it seems that this works only if you persist session vars into storage. If you don't do that, then since the CascadingAppState component gets reinitialized on a page refresh, the global vars are reinitialized and we are back to the beggining. Am I missing something?