Any web application has two main execution steps, first knowing the request and depending on the type of the request sending out an appropriate response. MVC application life cycle is not different it has two main aspects, first creating the request object and second sending our response to the browser.
Creating the request object,
The request object creation has four major steps. The following is a detailed explanation of the same.
Step 1 - Fill route
MVC requests are mapped to route tables which in turn state which controller and action to be invoked. So if the request is the first request the first thing is to fill the route table with routes assortment. This filling of the route table happens in the global.asax file.
Step 2 - Fetch route
Depending on the URL sent “UrlRoutingModule” searches the route table to create the “RouteData” object which has the details of which controller and action to invoke.
Step 3 - Request context created
The “RouteData” object is used to create the “RequestContext” object.
Step 4 - Controller instance created
This request object is sent to the “MvcHandler” instance to create the controller class instance. Once the controller class object is generated it calls the “Execute” method of the controller class.
Creating a Response object
This phase has two steps executing the action and finally sending the response as a result of the view.
Liked By
Write Answer
What is MVC application life cycle?
Join MindStick Community
You have need login or register for voting of answers or question.
Shikhar Arora
25-Dec-2019Any web application has two main execution steps, first knowing the request and depending on the type of the request sending out an appropriate response. MVC application life cycle is not different it has two main aspects, first creating the request object and second sending our response to the browser.
Creating the request object,
The request object creation has four major steps. The following is a detailed explanation of the same.
Step 1 - Fill route
MVC requests are mapped to route tables which in turn state which controller and action to be invoked. So if the request is the first request the first thing is to fill the route table with routes assortment. This filling of the route table happens in the global.asax file.
Step 2 - Fetch route
Depending on the URL sent “UrlRoutingModule” searches the route table to create the “RouteData” object which has the details of which controller and action to invoke.
Step 3 - Request context created
The “RouteData” object is used to create the “RequestContext” object.
Step 4 - Controller instance created
This request object is sent to the “MvcHandler” instance to create the controller class instance. Once the controller class object is generated it calls the “Execute” method of the controller class.
Creating a Response object
This phase has two steps executing the action and finally sending the response as a result of the view.