Separating behavior code from layout code, and developers separating UI code that adheres to the SRP.
The Blazor framework radically increases productivity.
A longstanding best-practice in user interface development is to separate behavior code from layout code.
While the Blazor framework radically increases productivity with rich in-browser applications, it’s up to the developer to separate UI code that adheres to the Single Responsibility Principle (SRP).
This session dives into how to properly implement Model-View-Controller in Blazor applications, whether it be hand-rolled or using the BlazorMVC nuget package.
