The “Middleware” pipeline is the main mechanism of ASP.NET Core to process the request and create the response.
ASP.NET Core is the web framework (development + runtime), which is the next generation of ASP.NET. It is based on .NET Core so that it can be distributed as modular framework.
I tend to create a lot of test web sites and applications in Visual Studio for learning purposes. Now I have ended up hosting many unused sites in IIS Express. Let’s clean up them.
DI(Dependency Injection) becomes the must-have patterns in any applications. MVC does work with any DI Containers such as Ninjet or Unity. MVC also provides the “Dependency Resolver” feature to make DI much easier.
Actions are public methods in controller classes. MVC provides attributes to tweak how the actions can be selected based on the name or the request verbs.
In the recent Web development environment, it is not rare that you need to reference many CSS and JS files across the site. Rather than reference them one by one, MVC 4 provides the “Bundling” feature that combine style or script files into a single resources.
The “Application_Start()” method in the “Global.asax” is the entry point of the MVC web application. Routes, areas, and global filters are initialized here. MVC 4 project templates provide a little bit different way of initializing these features.
IMHP, MVC 3 was a nice enhancement from the previous versions of MVC. Especially, the “Razor” syntax became the corner stone of ASP.NET MVC programming.
MVC evolves so fast and it is hard to keep up with the changes. What’s new in MVC 4 then?