The difference between WebForms and MVC

WebForms is familiar to an ASP. I've come into contact with WebForms from the beginning of the programmer, and I personally think that one of the features of WebForms is the frequent application of server-side controls and the code behind. So before chatting with a friend (Java programmer), he would often be more contemptuous of the said, ASP. NET development is very simple, not just drag some controls, write a small amount of code. Often hear these words, I never go to refute, because with a not knowledgeable people arguing, can only be a waste of time, so I just smiled. When I learned from the new ASP. NET, I felt that the MVC development pattern was quite popular, so I started to look at the MVC definition and compared it with the previous WebForms.

By comparison I think MVC's page response time is faster. Second, bandwidth consumption is less. The main factors that affect WebForms page speed are server-side space and code behind. The MVC pattern is more clearly divided, and the view layer is the presentation of the data, pure HTML. The controller layer is responsible for the client request, which is primarily a logical design. The model layer is the extraction of data, usually the connection to the database.

In the article I learned, I found that the author proposed a more granular layering, that is, between the view layer and the controller layer, there is a viewmodel layer to complete the data returned by the controller layer to integrate, and then passed to the view layer display, The other is the busniess layer, which exists between the controller layer and the model layer, which consolidates the data returned from the database and then transmits it to the controller layer.

The above is my webforms and mvc some understanding, should still exist to understand there is no place, hope to see this article of friends advice. We can discuss the research together and make progress together.

The difference between WebForms and MVC