Models and Data Entry

Abstract

Over the last few chapters, you’ve learned in some detail about how ASP.NET MVC lets you separate your HTML generation and application logic concerns using views and controllers. But most web applications ultimately revolve around data. Even if the user interface is very sophisticated and customized, it’s typically all about letting users browse and edit information. In MVC architecture, we use the term models for the data objects being passed between controllers and views. These models can be sophisticated domain models that encapsulate business logic and are persisted as entities in a database, or they can be just simple view models that are never saved and merely hold a set of properties that a view can render.