MVC Architecture

This Article helps you to Understand ASP.NET MVC Architecture

Asp.Net MVC is a full replacement for standard ASP.NET Web Forms. Because it is built on top of ASP.NET, developers can create MVC applications using almost all of ASP.NET's features. There won't be any page loads, illusions of state, page life cycles, or anything else of the sort.

Maintaining a separation of concerns is the whole point of utilising the Model View Controller design pattern. Your controller is no longer burdened by several connections to the ASP.NET runtime or the ASPX page.

Model
Model: Model represents the shape of the data. A class in C# is used to describe a model. Model objects implements the logic for the data domain of the application. It is used to retrieve and store model state in a database such as SQL Server database.
Model represents the data.

Controller
The controller handles the user interaction.
The user typically uses the view to initiate an HTTP request, which the controller responds to. The controller responds with the relevant view after processing the request.
The request handler is the controller.

View:
A view is a user interface in MVC. It is used to build the application's web pages. View allows users to alter model data while also displaying it to them. In ASP.NET MVC, the view is composed of HTML, CSS, and a special syntax known as Razor syntax that facilitates communication with the model and the controller. In an MVC application, the controller processes and responds to user requests and input while the view just shows information.