The Model-View-Controller (MVC)
architectural pattern separates an application into three main components: the
model, the view, and the controller. The ASP.NET MVC framework provides an
alternative to the ASP.NET Web Forms pattern for creating MVC-based Web
applications. The ASP.NET MVC framework is a lightweight, highly testable
presentation framework that (as with Web Forms-based applications) is
integrated with existing ASP.NET features, such as master pages and
membership-based authentication. The MVC framework is defined in the System.Web.Mvc namespace and is a
fundamental, supported part of the System.Web
MVC is a standard design pattern
that many developers are familiar with. Some types of Web applications will
benefit from the MVC framework. Others will continue to use the traditional
ASP.NET application pattern that is based on Web Forms and postbacks. Other
types of Web applications will combine the two approaches; neither approach
excludes the other.
The MVC framework includes the
Model: MVC model is
basically a C# or VB.NET class. A model is accessible by both controller and
view. A model can be used to pass data from controller to view. A view can use
model to display data in page.
View: View is an ASPX
page without having a code behind file. All page specific HTML generation and
formatting can be done inside view. We can use inline code (server tags) to
develop dynamic pages. A request to view (ASPX page) can be made only from a
controller’s action method.
is basically a C# or VB.NET class which inherits System.Mvc.Controller. Controller is a heart of the entire MVC
architecture. Inside Controller’s class action methods can be implemented which
are responsible for responding to browser OR calling views. Controller can
access and use model class to pass data to views. Controller uses ViewData to pass any data to view.
The MVC pattern helps you create
applications that separate the different aspects of the application (input
logic, business logic, and UI logic), while providing a loose coupling between
these elements. The pattern specifies where each kind of logic should be
located in the application. The UI logic belongs in the view. Input logic
belongs in the controller. Business logic belongs in the model. This separation
helps you manage complexity when you build an application, because it enables
you to focus on one aspect of the implementation at a time. For example, you
can focus on the view without depending on the business logic.
For more contents on ASP.Net MVC click here.