ASP.NET Web Forms or MVC. Which is the Best and the Fastest? [closed]

Hard to talk like this, it's better ..

When we deal with programming types, a lot will depend on your programming knowledge, and of course in the language in question.

The Web Forms.

As a general knowledge, it is such a catch and drag.

It has its importance, of course, it is simpler to use, but the code behind usually ends up having a dirty code, which depending on your application can be difficult.

Nowadays, it is becoming oblivious, if I may say so, or rather, disuse, although Microsoft says it will not be discontinued, it is not part of ASP.NET 5 , so it is out of some resources that this new version can bring.

The MVC

• Templates . Model objects are the parts of the application that implement the logic for the application's data domain. Often, model objects retrieve and store the state of the model in a database. For example, a Product object can retrieve information from a database, operate on it, and then write updated information back to a Products table in a SQL Server database. In small applications, the model is often a conceptual rather than a physical separation. For example, if the application only reads a dataset and sends it to view, the application will not have a physical model layer or associated classes. In this case, the data set assumes the role of a model object.
• Views. Views are the components that display the application's user interface (UI). Normally, this UI is created from the model data. An example would be an edit view of a Products table that shows text boxes, drop-down lists, and checkboxes based on the current state of a Product object.
• Drivers . Controllers are the components that handle user interaction, work with the model, and ultimately select a rendering view that shows this UI. In an MVC application, the view only shows information; the controller handles and responds to user input and interaction. For example, the controller handles query string values and passes these values to the template, which in turn can use these values to query the database.

Conclusion

If you are a beginner now, that is, studying to learn, I would recommend MVC , for a simple and obvious logic, it is the architecture of the moment, and where guys are betting chips, or

But if you are an experienced programmer, already familiar with WebForms , I ask you, is not it time to upgrade?

References:

Overview of ASP.NET MVC

Major changes in ASP.NET 5 and MVC

There are several differences between the technologies mentioned. MVC is an old standard, but ASP.NET MVC is the natural evolution of ASP.NET.

If you look at the designer side, Asp.NET MVC is much more compatible with the devices we have today. It generates pure HTML, very different from Webforms where a lot of html is injected for support. MVC has no postback and is RestFull.

I would say yes, that MVC is faster than WebForms.

I leave here an article from Israel Aece on this subject: COMPARATIVE: MVC VS. WEBFORMS

Att

William

On the one hand we have years of experience and evolution, with a vast amount of tools that greatly increase productivity, making development fast and easy on WebForms.

On the other side, we have a framework that aims at a more organized division, making it easier to manage large and complex applications, allowing better test-driven development support and giving the developer full control of application behavior.

I think the most appropriate answer to the above question is: both! It will depend a lot on the application that will be developed, the resources involved, the term, and why not, the price. Knowing the differences, the benefits and pitfalls of each of the architectures, the answer will be clear for each situation.

REf: link