(i) Introduction to ASP. NET MVC

(1) What is ASP. NET MVC?

HttpHandler is the underlying mechanism of ASP. If you use HttpHandler directly, it is more difficult to develop, and the workload is great. As a result, the framework for advanced encapsulation, such as ASP. NET MVC, ASP. NET WebForm, simplifies development, and their bottom layer is still implemented HttpHandler, HttpRequest and so on. For example, the core of ASP. NET MVC is still the implementation of the IHttpHandler interface Mvchandler.

(2) What is the relationship between ASP. NET WebForm and ASP?

　　Is the framework for the HttpHandler package, and ASP. NET WebForm is a framework that Microsoft invented to make the development of ASP. NET-like development WinForm, with many drawbacks; ASP. NET MVC uses the idea of MVC, more in line with the development of modern projects, so ASP. NET MVC is gradually replacing ASP. NET WebForm.

(3) Why is ASP. NET MVC better?

Programmers have greater control, no garbage code, and programmers have clearer controls over the running process, so security, performance, architecture, etc. are clearer. WebForm and ASP. NET MVC is just the opposite of the "Getting Started" and "deep" two features. The introduction of ASP. NET MVC is difficult, deep and simple, and WebForm is simple and difficult to get started.

(4) What is the MVC pattern? Model, view, Director (Controller)

Model is responsible for the transfer of data between the View and Controller: The content entered by the user is encapsulated as a model object, sent to the controller, the data to be displayed is placed in the model by the controller, and then thrown to the view to display. The Controller does not interact directly with the View.

(5) ASP. NET MVC does not have any relationship with the "three-tier architecture". The UI layer in a three-tier architecture can be implemented with ASP.

(6) ASP. NET MVC has a strong dependency on conventions, and the benefit is that you can reduce the configuration.

(i) Introduction to ASP. NET MVC