Out of the box, Microsoft provides a tremendous amount of information, and supporting material to get started working with MVC Routing, Controllers, Models and Views. No doubt these are important to know first, however very little consistent guidance is provided for how to build models that can be used to properly separate concerns while being the conduit to transfer data from controller to view.
FatModel fills this gap for both those web developers that are new to ASP.Net MVC, as well as for more seasoned developers that want a consistent methodology to develop web based applications.
The FatModel framework provides intuitive and unobtrusive base classes and interfaces for models and controllers that facilitate consistent sub classing and usage of MVC Models. Included is a solid set of best practices for MVC, which can be used with FatModel, or used independently with any ASP.Net application.
FatModel is based on a common best practice known as Skinny Controller, Fat Model, Dumb View. The classes and interfaces provided make it easy to implement and conform to this best practice.