What ASP.NET programming model to choose?

Question

Summary

I am an experienced programmer with many years of experience developing Windows Forms using different programming languages, as was already said in this question:

Will WPF learn my skills in ASP.NET?

ASP.NET or any web programming language is not natural for me to research or use. Although I am not familiar with web technologies, my curiosity about it is growing and growing. In addition to this, I know about the market on which web programming is based. I would like to expand my knowledge and experience on the Internet, although it would be easy to know what I'm talking about, instead of speculating.

My experience as a developer of information and technological systems allows me to understand concepts and some of the basics. I know that web applications, for example, have no state, and I need to use session or viewstate variables to maintain the information that the user is working with live, otherwise I would lose them.

I also understand the basics of Ajax-based controls, such as UpdatePanel, which should only refresh or refresh part of the user interface page, and not reload everything through the connection.

I can get that CSS defines styles for your page sections and that you can radically change your site by simply changing the CSS link.

I also know about master pages that I really don't understand. Actually.

Programming model

I just watched this video about choosing the right model for me / my application:
Choosing the Right Programming Model

If it looks like ASP.NET MVC, which I thought was the best approach, more for veteran web developers, people who are comfortable with web applications.

I used a lot of DataBinding in Windows Forms, and WebForms seems to be more than what I am looking for in ASP.NET until they say that MVC allows Unit Testing, TDD and Agile methods, which I follow as a certified professional Scrum Master.

I am a bit involved in what will be more natural for me, speaking of a programming model.

Questions

• Considering my knowledge base and my experience, what programming model do you think will be more convenient for me?

• When choosing one of them, let me familiarize myself with ASP.NET in order to try another model one day?

• In the video about choosing the programming model that sat on ASP.NET, I heard about DataBinding when using Web Forms, but did not mention DataBinding in the MVC model. Is there a possible DataBinding in MVC?

Finally

I am very confused about all of this ASP.NET stuff.

Answer 1

This is so subjective that it probably closes and no matter what answer we give, it will most likely receive downvotes, as well as ups, BUT ....

Given your familiarity with WinForms development, I would say go to WebForms if you want to get up and running as quickly as possible. Even if you eventually switch to MVC, you will be more comfortable working with WebForms at the beginning, while you will learn all the possibilities of web development, so this will be less shock for your system.

And that’s why I don’t get attached to being prejudiced by others who consider it, I understand that there are many advantages to MVC, but, in my own humble opinion, I think it's stupid to get into “Which is better.” I give this answer because he asked (to paraphrase) "what will be easier for me to understand and start with."

Edit I think I just addressed the first two questions above ...

Third, data binding in MVC is slightly different, but not so much. Access to data under the hood is the same, but you are strictly controlling the output.

See this post for a quick look at a good answer explaining how to make a simple “anchor”. The questionnaire in this question was less familiar with MVC and asked how to do data binding in the drop-down list in MVC. The answer was good and pointed to a good article.

ASP.NET MVC Structure and Binding

Answer 2

just go with asp.net mvc.

it will really improve the way you burn Windows applications.

his mistake is to try to find the closest similar paradigm to what you are used to. It is almost better to have it completely different, because it will restrain what looks like, but not quite the same.

Mostly web forms were microsoft, which tried to simplify the work with web materials coming from the world of windows. But it is akin to what comes from the sailing background and develops a “car” that you control, as if it were a sailing boat. You just better learn how to drive a car, ride when you need to drive a car, sail when you need to sail.

therefore, you will have to make an effort to understand the web material. It is not too complicated, it may take a little time. But there is a huge resource of knowledge that you can rely on.

mostly come to web development, and your bowl is empty ready to learn :)

Answer 3

I am using WebForms and I came from VB6. It was strange from the very beginning when I needed to learn about the page loop.