Explain ASP.Net Request MVC lifecycle?

Explain ASP.Net Request MVC lifecycle?
When the user sends from the browser, it’s been handled by Routing concept and which navigates it to the appropriate Controller where controller picks up the relevant View and send it as a response to the User.
Routing: Asp.net Routing is the first step in MVC request cycle.
MvcHandler: The MvcHandler is responsible for initiating the real processing inside ASP.NET MVC. MVC handler implements IHttpHandler interface and further process the request by using ProcessRequest method
Action Execution: After the particular controller gets instantiated ActionInvoker determines which specific Action method needs to be execute. ActionInvoker uses ActionNameSelectorAttribute and ActionMethodSelectorAttribute to select Action method for execution
Rendor View Result: The action method receives user input, prepares the appropriate response data, and then executes the result by returning a result type
View Engine: The first step in the execution of the View Result involves the selection of the appropriate View Engine to render the View Result. It is handled by IViewEngine interface of the view engine. By default Asp.Net MVC uses WebForm and Razor view engines.
View: Action method may returns a text string, a binary file or a JSON data or javascript formatted data. The most important Action Result is the ViewResult, which renders and returns an HTML page to the browser by using the current view engine.