ASP.NET Web Forms or MVC. What’s Best and Fastest?

Asked

Viewed 4,358 times

2

I have Great Knowledge in Webform, but I see a lot of growth in MVC. Will Webform be extinct ? MVC is better than Webform.

asp.net-mvc-5

  • http://softwareengineering.stackexchange.com/questions/95212/when-to-favor-asp-net-webforms-over-mvc

  • Related: The MVC and Webforms paradigms (with code-Behind) are mutually exclusive? and End of ASP.NET Webforms?

  • This may help: http://answall.com/q/111209/101 and http://answall.com/a/49094/101

  • 5

    Webforms is considered legacy technology. I’m not saying you should not use it anymore, but know that there will be no further important evolution in it. In fact ASP.Net MVC is also practically legacy. If you want to go into something more modern, the path is ASP.Net Core (formerly called ASP.Net 5 or ASP.Net MVC 6, see http://answall.com/q/52158/101). It has something on the . Net Core as a whole: http://answall.com/q/40671/101.

3 answers

6


Hard to talk like that, it’s better..

When it comes to types of programming, a lot will depend on your knowledge of programming, and of course on the language in question.

The Web Forms.

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

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

Nowadays, it has been falling into oblivion, if I may say so, or rather disuse, despite Microsoft saying that it will not be discontinued, it is not part of the ASP.NET 5, then stay out of some features that this new version can bring.

The MVC

The acronym MVC comes from Model, View and Controller, an architecture that already exists for a long time, is more complex yes, than the WebForms but enables cleaner code, by giving tools that encompass the entire application, and of course, this is the team that comes into play in version ASP.NET 5

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

Completion

If you are a programmer who is starting now, that is, studying to learn, I would recommend the MVC, by a simple and obvious logic, is the architecture of the moment, and where the guys are betting the chips, IE, come around a lot of update.

But if you are an experienced programmer, already familiar with the WebForms, I ask you, isn’t it time to catch up?

References:

Overview of ASP.NET MVC

Key changes in ASP.NET 5 and MVC

  • Thank You For The Information.

  • @Andersondefreitasmigloranza no formality required, use the comet fields for questions etc. See our help center: http://answall.com/help and http://answall.com/help/someone-answers

1

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 a pure HTML, quite different from Webforms where it is injected a lot of html for support. MVC has no postback and is Restfull.

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

An article by Israel Aece on this subject: COMPARATIVE: MVC VS. WEBFORMS

Att

William

1

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

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

I believe the most appropriate answer to the question upstairs is: the two! It will depend a lot on the application that will be developed, the resources involved, the deadline, and why not, the price. Knowing the differences, benefits and obstacles of each of the architectures, the answer will be clear for each situation.

Ref: http://www.devmedia.com.br/artigo-net-magazine-65-asp-net-webforms-x-mvc/13896

Browser other questions tagged asp.net-mvc-5

You are not signed in. Login or sign up in order to post.