Sep 21, 2020 09:29 PM|DA924|LINK
I am learning MVC and this is my first application in MVC.
I would say come out the gate the right way.
An MVC model contains all of your application logic that is not contained in a view or a controller. The model should contain all of your application business logic, validation logic, and database access logic. A view should contain only logic related to
generating the user interface.
A controller should only contain the bare minimum of logic required to return the right view or redirect the user to another action (flow control). Everything else should be contained in the model.
In general, you should strive for fat models and skinny controllers. Your controller methods should contain only a few lines of code. If a controller action gets too fat, then you should consider moving the logic out to a new class in the Models folder.
A sample MVC solution implementing the concepts being discussed.