What is MVC Architecture?
Answer Posted / punit agrahari
Model View Controller architecture (or pattern) allows us
to separate different parts of our applications into tiers
to fulfill this need.
MVC Overview
Model View Controller architecture aims to separate an
application into three parts:
Model: It is the business logic of an application. From an
object oriented perspective it would consist of a set of
classes that implement the critical functionality of an
application from a business point of view.
View: It can consist of every type of interface given to
the user. In ASP.NET the view is the set of web pages
presented by a web application.
Controller: This part of the architecture is the most
difficult to explain, hence the most difficult to implement
in many platforms. The controller is the object that allows
the manipulation of the view. Usually many applications
implement Model-Controller tiers that contain the business
logic along with the necessary code to manipulate a user
interface. In an ASP.NET application the controller is
implicitly represented by the code-behind or the server
side code that generates the HTML presented to the user.
Implementing MVC in ASP.NET
A basic diagram that would help us understand perfectly the
specific parts that implement the Model View Controller
architecture in an ASP.NET application is presented below:
| Is This Answer Correct ? | 8 Yes | 4 No |
Post New Answer View All Answers
Why do we need struts?
What do you mean by dynaactionform?
At the point, you should go for struts framework?
What is the role of action class in struts?
Why was reload removed from struts (since 1.1)?
What is the use of jsonvalidation?
Are struts and shocks the same?
What is pojo in struts2?
What is the purpose of '@customvalidator'?
What is difference between interceptors and filters?
What is the purpose of @customvalidator annotation?
What is discontinuous strut?
What is struts xml?
What is struts validator framework?
Which interceptor is responsible for file upload support?