Learn Basics Of MVC Architecture

Basically, MVC makes the design of the application into three layers namely Model, View, and Controller. Each of these components are built to handle different aspects of the application.

Model layer represent the objects in our Application. Model is also a class which has all the objects and its properties and methods defined in it.

View Layer has all the html controls which define the UI of the application. Here in MVC, we don’t have drag and drop option for controls as we don’t use server controls. Instead we use Razor Engine available with Visual Studio by default which helps in rendering the View.

Views are files with .cshtml extensions. .cshtml contain both html and server code.

And also, using ‘@’, we can access C# code so that in our page which can access server side dynamic data.

Controller basically handles the request from user. It is the heart of the MVC application as everyone say. It is responsible to handle the request and return a response to user by loading appropriate View with data from Model.

Controller is nothing but a class with a group of methods called actions. And Every action method returns view. A View can be anything like it can be xml or html or JSON etc.

Controller maps the incoming user requests to appropriate Controller actions with the help of process called Routing.

Routing process internally creates a table called ‘Route Table’ which describes which action to be taken for each request from user. The route table is created during the Application Start event. Routes are URL patterns created dynamically based on incoming request.

In Global.asax, in Application_Start () event all the routes configured in application must be registered.

Generally, Data Access Layer is again a separate layer along with MVC Layers, like as we have in asp.net web application. DAL can contact Database and return result to Model.

Another important point to remember is, MVC is not totally new framework. It is built on top of asp.net, so all the features available in asp.net can be used in MVC as well. So it is called as Asp.net MVC.

Using MVC, once the application is developed, we can use the same logic for either asp.net MVC Application or phone app just by changing the View Layer of the application. So MVC also enhances reusability.

We can say MVC follows Front Controller approach because here it is that Controller which handles all requests whereas ASP.net Web Application follows Page Controller approach. i.e It is Page level at which incoming request is handled and act accordingly.

According to the requirement of application, an appropriate framework can be selected to develop the application.