ASP.NET MVC Architecture
ASP.NET MVC is a free website building framework for the development of websites and web applications using the framework of .NET and the C# language. For Front End Development we can use React.js and Angular.js with the support of JavaScript, jQuery, Html, and CSS.
ASP.NET Web framework is based on (MVC) Architecture, and allows software engineers to develop state of the art dynamic web applications using .Net MVC framework. It enables the software engineer to separate the Business logic Views and Web Controller for fast and easy development. Using .NET framework developers can easily expand application architecture for feature enhancement in the future.
Prerequisite of Creating the ASP.NET Applications.
For creating ASP.NET applications you just need to know the basic knowledge of C#, .Net Architecture, and Command of Visual Studio.
ASP.NET Architecture
MVC Stands for Model Views and Controller. In .NET Application, we can separate the application into three parts: Model, View, and Controller.
Model
In the .net Application when we create the Data Access layer then we create Models. We write our business logic in the Data Access Layer. After that, we run Migrations for Connecting / Mapping our Models with Database using the help of Entity framework. Models represent the data of the application.
View
Views are the user interface in .NET Framework. Views help us to show the model data to the application users. We create views in .Net Framework using HTML, CSS, and sometimes with the help of React.js and Angular.js and sometimes with Razor pages that is the easy way for communicating the front end with the back end.
Controllers
The controller in the .Net framework is the request handler. When a user sends the HTTP request from the front end to the controller then the controller manipulates the models and displays the appropriate data to the user.
In the below image, you can see the communication between the Client and MVC Architecture Application,
ASP.NET Version History
|
Visual Studio |
.NET Framework |
Released Date |
Features |
MVC 1.0 |
VS2008 |
.Net 3.5 |
13-Mar-2009 |
- MVC architecture with webform engine
- Routing
- HTML Helpers
- Ajax Helpers
- Auto binding
|
MVC 2.0 |
VS 2008, |
.Net 3.5/4.0 |
10-Mar-2010 |
- Area
- Asynchronous controller
- Html helper methods with lambda expression
- Data Annotations attributes
- Client-side validation
- Custom template
- Scaffolding
|
MVC 3.0 |
VS 2010 |
.Net 4.0 |
13-Jan-2011 |
- Unobtrusive JavaScript validation
- Razor view engine
- Global filters
- Remote validation
- Dependency resolver for IoC
- View Bag
|
MVC 4.0 |
VS 2010 SP1,
VS 2012 |
.NET 4.0/4.5 |
15-Aug-2012 |
- Mobile project template
- Bundling and minification
- Support for Windows Azure SDK
|
MVC 5.0 |
VS 2013 |
.NET 4.5 |
17-oct-2013 |
- Authentication filters
- Bootstrap support
- New scaffolding items
- ASP.Net Identity
|
MVC 5.2 - Current |
VS 2013 |
.NET 4.5 |
28-Aug-2014 |
- Attribute-based routing
- bug fixes and minor features update
|
ASP.NET MVC 5.2.3 |
VS 2015 |
.NET 5.2.3 |
9 February 2015 |
|
.NET 5.2.4 |
VS 2017 |
.NET 5.2.4 |
12 February 2018 |
|
.NET 5.2.5 |
VS 2017 |
.NET 5.2.5 |
2 May 2018 |
|
.NET 5.2.6 |
VS 2017 |
.NET 5.2.6 |
11 May 2018 |
|
.NET 5.2.7 |
VS 2017/2019 |
.NET 5.2.7 |
29 November 2018 |
|
Conclusion
As a software engineer having 3+ years of working in the industry, I have developed many applications using ASP.NET, MVC, and MVC Core, and .NET Web API. Now I want to share my knowledge with the online community. I found .Net MVC Architecture is the best for creating state-of-the-art applications You can also create Microservices / Cloud Native Applications using, Net Framework.