Asp.net MVC life cycle

Question

What is the Asp.net MVC life cycle? I have visited the multiple tutorial websites and observed that every websites define its on different ways.... Even heading also different...I need experts comment on that..And provide the exact MVC life cycle.... There are some links what are i am saying --- https://www.tutorialspoint.com/asp.net_mvc/asp.net_mvc_life_cycle.htm https://www.dotnetinterviewquestions.in/article_explain-mvc-application-life-cycle_210.html https://dotnettekki.com/aspnet-mvc-page-life-cycle/ https://www.c-sharpcorner.com/UploadFile/00a8b7/Asp-Net-mvc-life-cycle/ https://blogs.msdn.microsoft.com/varunm/2013/10/03/understanding-of-mvc-page-life-cycle/ https://www.dotnettricks.com/learn/mvc/aspnet-mvc-request-life-cycle

Mageshwaran R · Answer

Hi, Please refer the below link, it might helps you https://www.c-sharpcorner.com/UploadFile/00a8b7/Asp-Net-mvc-life-cycle/

Kapil Gaur · Answer

If you want this crisp then Step 1 - Application start Step 2- Route Table creation (Fill Route) Step 3 - Fetch route Step 4 - Request context created Step 5 - Controller instance created Step 6 - Respective action executed Step 7 - Creating Response object this is enough in that case.

Sonu Gupta · Answer

Hi kapil, Thanks for response, I discussing about the steps (Heading's) invloved in MVC life cycle, Not a internal process happened during life cycle of MVC. How to define summarize this For exaple this - Step 1 - Fill route Step 2 - Fetch route Step 3 - Request context created Step 4 - Controller instance created Step 5 - Creating Response object

Kapil Gaur · Answer

The crux of all the links given below should be like this. You must know below things when we talk about ASP.NET MVC life cycle. 1. At first web browser or an application sends request. 2. RouteTable come into the picture. Every ASP.NET MVC application has a RouteTable. This routetable is responsible to map the mvc requests to particular controller. Whenever the Application Start the Application_Start events will get called and it will call the method RegisterRoutes which will send the collection of Routes as the parameter and the routes will be added to this Collection which is a Dictionary of NamedMaps. And this is how routetable is created for first time. 3. URL Routing module basically intercepts all the requests. It wraps up the current HttpContext in an HttpContextWrapper object. The module then instantiates a new HttpHandler based on the RouteTable and passes the RouteContext to the new handler’s constructor. 4. MVCHandler using the ProcessRequest() method creates the required controller using controller factory. 5. Controller Executes and using RouteData executes respective action. 6. After that request is processed and Controller typically either executes either the RedirectToAction Method or the RenderView Method. When you call a controller’s RenderView() method,the call is delegated to the current ViewEngine’s RenderView() method. So in this way either it gets redirected or it returns the result as view or some other kind of result. This is high level picture of MVC life cycle that a programmer must know. This can be drilled down further for deep understanding. You can read this article also which is available on Microsoft Doc. Network. https://blogs.msdn.microsoft.com/varunm/2013/10/03/understanding-of-mvc-page-life-cycle/ I hope this help you.