Comparison between ASP. net mvc and webform

Webform

Easy to get started. You can drag and drop the page control directly and control the properties, methods, and events of the control through a visual form.

Difficult to grasp, it has a complex page lifecycle and event-driven mode.

It is difficult to conduct unit tests. The MVP model in the later stages solved the problem of unit tests to a certain extent.

Encapsulation is high and difficult to expand.

ASP. NET MVC

Design for testability, so unit test support is good.

Front-end and back-end staff are easier to work.

Submit a form based on the traditional web development method.

Fully open-source, easy to expand, and more plasticity. (The Source Code cannot be re-released after modification)

ASP. net mvc is not a substitute for webform, but a choice for web development. Each development method has its own advantages and disadvantages.