Thank You - great talk 🙂 I just remembered WebForms: The ViewState solved the issue quite well. ViewState was one of the most powerfull features of WebForms. Sadly it was the most missused and not understood feature as well, which lead to a bad rap...
Very interesting and useful. Overlaps some methods I was trying out with localstorage persisted services so plenty to think about. BTW the failure to restart the app was because previous app tabs were still open in the browser (several in your case). You have to make sure all browser tabs are closed as Visual Studio does not always close off the tabs it started up with Blazor.
Thanks for the excellent presentation and great info!
Thank You - great talk 🙂
I just remembered WebForms: The ViewState solved the issue quite well. ViewState was one of the most powerfull features of WebForms. Sadly it was the most missused and not understood feature as well, which lead to a bad rap...
Very interesting and useful. Overlaps some methods I was trying out with localstorage persisted services so plenty to think about. BTW the failure to restart the app was because previous app tabs were still open in the browser (several in your case). You have to make sure all browser tabs are closed as Visual Studio does not always close off the tabs it started up with Blazor.
Thank you so much Carl!!
Excellent !!
wish there was just ability to declare lifetime of component/page as scoped with directive, it would already solve a half of the state persistence job
Link to source code?
I am trying this in Blazor Client Side with .Net 8 but I my AppState is null when I click a button :(