ASP.NET MVC Architecture - TutorialsTeacher

Follow Us

Articles.NET

• C#
• C# OOP
• ASP.NET Core
• ASP.NET MVC
• LINQ
• Inversion of Control (IoC)
• Web API

JavaScript

• JavaScript
• TypeScript
• jQuery
• Angular 11
• Node.js
• D3.js
• Sass

Programming

• Python
• Go lang
• HTTPS (SSL)
• Regex

Database

• SQL
• SQL Server
• PostgreSQL
• MongoDB

Online TestsArticles

• ASP.NET MVC - Get Started
• MVC Architecture
• MVC Version History
• Create First MVC App
• MVC Folder Structure
• Routing
• Controller
• Action method
• Action Selectors
• ActionVerbs
• Model
• View
• Integrate Model, View & Controller
• Model Binding
• Create Edit View
• Razor Syntax
• Html Helpers
• Exception Handling
• Validation
• Layout View
• Partial View
• ViewBag
• ViewData
• TempData
• Filters
• ActionFilters
• Bundling
• ScriptBundle
• StyleBundle
• Area

Entity Framework Extensions - Boost EF Core 9   Bulk Insert   Bulk Delete   Bulk Update   Bulk Merge ASP.NET MVC Architecture

Here, you will learn an overview of MVC architecture.

The MVC architectural pattern has existed for a long time in software engineering. All most all the languages use MVC with slight variation, but conceptually it remains the same.

Let's understand the MVC architecture supported in ASP.NET.

MVC stands for Model, View, and Controller. MVC separates an application into three components - Model, View, and Controller.

Model: Model represents the shape of the data. A class in C# is used to describe a model. Model objects store data retrieved from the database.

Model represents the data.

View: View in MVC is a user interface. View display model data to the user and also enables them to modify them. View in ASP.NET MVC is HTML, CSS, and some special syntax (Razor syntax) that makes it easy to communicate with the model and the controller.

View is the User Interface.

Controller: The controller handles the user request. Typically, the user uses the view and raises an HTTP request, which will be handled by the controller. The controller processes the request and returns the appropriate view as a response.

Controller is the request handler.

The following figure illustrates the interaction between Model, View, and Controller.

The following figure illustrates the flow of the user's request in ASP.NET MVC.

As per the above figure, when a user enters a URL in the browser, it goes to the webserver and routed to a controller. A controller executes related view and models for that request and create the response and sends it back to the browser.