Good video - thank you. 6:14 I think it is misleading to say that Razor Pages and MVC do not provide a component-based programming model. Both actually do. For Razor Pages and MVC, you can use Tag Helpers, Razor Components, View Components, and Partial Views.
Hi. Thanks for your comment. What I meant was, Razor Pages and MVC by themselves lack a component-based programming model, in the stricter sense of "Razor components". So, yes, if we consider Tag Helpers, View Components and Partial Views as components in a broader sense, you're definitely right; Razor Pages and MVC do support this model. Thanks for pointing it out.
Differences of three frameworks are clearly explained. Many thanks.
Thank you so much for your comment. You're welcome.
This is amazing!!! Thanks for your time in producing this video
Thank you so much for your comment. You're welcome.
Good video - thank you.
6:14 I think it is misleading to say that Razor Pages and MVC do not provide a component-based programming model. Both actually do.
For Razor Pages and MVC, you can use Tag Helpers, Razor Components, View Components, and Partial Views.
Hi. Thanks for your comment. What I meant was, Razor Pages and MVC by themselves lack a component-based programming model, in the stricter sense of "Razor components". So, yes, if we consider Tag Helpers, View Components and Partial Views as components in a broader sense, you're definitely right; Razor Pages and MVC do support this model. Thanks for pointing it out.
Which one do you recommend ?
I recommend Blazor going forward because it is full stack and can be used for building both server-rendered and client-rendered web UIs.
Is the CSR that you mentioned equivalent to WebAssembly?
Hi. Sorry for the late reply. Yes, you are right. CSR (Client-Side Rendering) refers to a component running in Blazor WebAssembly.