Application life cycle of MVC in c#

The ASP.NET MVC Process

In a MVC application, no physical page exists for a specific request. All the requests are routed to a special class called the Controller. The controller is responsible for generating the response and sending the content back to the browser. Also, there is a many-to-one mapping between URL and controller.

When you request a MVC application, you are directly calling the action method of a controller.

When you request http://mysite/Controller1/method1, you are actually calling Controller1's method1. We will see how our request is routing to an ActionMethod of a controller.

for more please follow the link below, this may helps you more to learn,

http://www.c-sharpcorner.com/UploadFile/00a8b7/Asp-Net-mvc-life-cycle/

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Puneet Kankar9y ago

For more details please read this articles

http://www.dotnettricks.com/learn/mvc/aspnet-mvc-request-life-cycle

https://www.dotnetinterviewquestions.in/article_explain-mvc-application-life-cycle_210.html
Sundaram Subramanian9y ago
The ASP.NET MVC Process
In a MVC application, no physical page exists for a specific request. All the requests are routed to a special class called the Controller. The controller is responsible for generating the response and sending the content back to the browser. Also, there is a many-to-one mapping between URL and controller.
When you request a MVC application, you are directly calling the action method of a controller.
When you request http://mysite/Controller1/method1, you are actually calling Controller1's method1. We will see how our request is routing to an ActionMethod of a controller.

for more please follow the link below, this may helps you more to learn,

http://www.c-sharpcorner.com/UploadFile/00a8b7/Asp-Net-mvc-life-cycle/