It does not matter how slowly you go, so long as you do not stop.
By default, the Microsoft Visual Studio standard project template for ASP.NET MVC applications includes a Models folder. If you look around for some guidance on how to use it and information about its intended role, you quickly reach the conclusion that the Models folder exists to store model classes. Fine, but which model is it for? Or, more precisely, what’s the definition of a “model”?
In general, there are at least two distinct models—the domain model and the view model. The former describes the data you work with in the middle tier and is expected to provide a faithful representation of the domain entities. These entities are ...