Advantages and disadvantages of ASP. NET WebForm and MVC, asp. netwebformmvc

Advantages and disadvantages of ASP. NET WebForm and MVC, asp. netwebformmvc

Posted on my personal website, please clickRead!

Differences between aspnet mvc and WebForm

MVC vertically splits the code in the development process from the server to the browser, and the coupling between layers is very low, because it is encapsulated along the underlying development context, therefore, developers can understand the entire process flow. However, MVC has a major drawback, which deviates from the overall software development idea, that is, it cannot be encapsulated or encapsulated, so it cannot be reused. Who has seen components under mvc? Some are just off-the-shelf cases, and then they are modified. Because a component must involve control and display, but the two layers of mvc development are separated. MVC is only suitable for lightweight development, and the mvc mode is rarely used for desktop development. However, web development is lightweight. So far, all web development is lightweight. Because of the limitations of network hardware conditions, it is impossible to implement complex logic without any need. This is why MVC is very suitable for web development.
WebForm is a web development mechanism in front of Microsoft. It horizontally splits the code, and controls and displays are encapsulated together. It encapsulates the code from the developer's logic rather than the actual situation. This is why webform is easy to use. However, this is not conducive to developers' understanding of the underlying program transfer mechanism. In WebForm, view and controller are put together. When WebForm appears, a large number of components are generated, which is invisible in mvc mode. One of Microsoft's experiences is the rapid development of hardware. Code encapsulation improves development efficiency at the expense of operation efficiency, and sacrifices operation efficiency by improving hardware performance. However, Microsoft has made an empirical mistake in webform. This experience is not suitable for network hardware. network hardware should consider compatibility and be the national infrastructure. The flexibility of updating is far worse than that of a single machine. A large number of components cannot bring any advantages to WebForm due to hardware bottlenecks. After several years of development of webform, Microsoft felt that this would not work. When network hardware was developed, it was not known that it was the year of the monkey, so it copied the mature mvc, using Entity Framework to map databases and objects, it is obvious that it serves as the Model in mvc. Control and display through mvc.
The production relationship of webform is more advanced than mvc, but it is not suitable for the current productivity of network facilities. If it is suitable, it may take 10 years. Webform and mvc prove that production relations must be suitable for productivity. Even if they are powerful, Microsoft cannot change objective rules.

Advantages and disadvantages of asp net mvc Framework

Advantages of MVC:
1. It is easy to maintain during large-scale development and has good scalability.
2. You can have full control permissions on HTML, which is friendly to the front-end.
3. Ability to perform unit tests to ensure the implementation of functions.

Disadvantages:
1. There are not so many ready-to-use controls, and the development efficiency is relatively low (especially for cainiao)
2. It is difficult to process large data because there is no ready-made girdview control. Although the html structure generated by this control is extremely complex, it is very good for processing large amounts of complicated data. However, there are very few such massive and complex data on websites. Many cainiao use this cannon to attack mosquitoes, which is a waste and inefficient task. This control should not be recommended for website development.

The new cainiao and webform are good when rapid development is required.
Scalability is required. MVC is recommended for high control. However, the threshold for using this framework is relatively high. If you only understand the webform development form of asp.net, because webform has already done too many things for you, in other words, you do not know what real web development is like. On the contrary, asp users are more familiar with php.

MVC and webform have their own purposes.
However, you should not use the asp.net mvc framework:
You are not very familiar with Polymorphism
You don't like building applications on this framework
You rely on many third-party UI controls
You do not like to use open-source programs