With the first glance at Blazor, I have that idea - it's perfect for MVVM.
I started with MVVM on WPF apps many years ago and spent a lot of time with MVVMLight and Xamarin, so I immediately saw an advantage of it for Blazor as well.
1/3
#Blazor #BlazorBits
I started with MVVM on WPF apps many years ago and spent a lot of time with MVVMLight and Xamarin, so I immediately saw an advantage of it for Blazor as well.
1/3
#Blazor #BlazorBits
This is ComponentBase which I use for MVVM everywhere. The only problem is JS
You cannot use js methods in OnInitializeAsync, and data initialization in OnAfterRender looks wrong to me (at least it's not what docs propose).
2/3
You cannot use js methods in OnInitializeAsync, and data initialization in OnAfterRender looks wrong to me (at least it's not what docs propose).
2/3
And there are things like js-loading indicator which need to be started if the page loaded but the data not.
Much confusing
For now, I simply move all JS initialization to OnAfterRender permanently
Oh, the gist of this classes available here
gist.github.com/xakpc/6d15b7b1β¦
3/3
Much confusing
For now, I simply move all JS initialization to OnAfterRender permanently
Oh, the gist of this classes available here
gist.github.com/xakpc/6d15b7b1β¦
3/3
@threadreaderapp unroll
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
γ
