ASP.NET Learning Path

Question

I want to ask experienced ASP.NET developers how to climb the ASP.NET learning curve.

I am an experienced C ++ and C # developer with no experience with web applications.

I found that ASP.NET MVC and ASP.NET are two different technologies. I just want to ask:

• Are these two technologies compatible or will they replace ASP.NET MVC?
• If I want to learn ASP.NET MVC. Do I need to learn ASP.NET as a prerequisite?
• Can you recommend some training resources? Book? Video? Microsoft training is not paid: (

Many thanks

Answer 1

First of all, ASP.NET is a request / response pipeline. This means that you are granted access to the request and response flows, as well as some provisions, such as session, cache, security, etc.

In addition, there are 3 frameworks for generating HTML. The first and oldest is known as ASP.NET Web Forms. Since it was the only one, it is sometimes called ASP.NET, but this does not correspond to the current state of things. ASP.NET MVC is the second, and there is a third, known as ASP.NET Web Pages. All three of them have the same main ASP.NET request / response pipeline and session, cache API ... What is the difference between the way they generate HTML.

You can check my answer to this question for more information. Asp.Net Web Forms and Asp.Net Web Pages

And to answer your specific question - no web forms go away. Many use it, MS releases new versions.

Web forms are pretty good for people with a desktop background because it uses a control model that is familiar to desktop developers and also has something that mimics state. It also requires less knowledge of HTML, JS, CSS. ASP.NET MVC is the opposite. This gives you a lot of control, but requires a lot of knowledge about the network.

I personally prefer web forms for MVC for a number of reasons, which I will not list here, but even supporters of Web Forms (and especially me) admit that web forms are a pretty bad way to learn about the network, as it abstracts a lot of things . This gives you performance, security, etc., but it can lead to cases of abstraction leakage if you don’t know how the underlying infrastructure works, and it’s pretty easy to skip learning the details, because you know things just work ... for now it will not break and then you do not know where to start.

Ultimately, the choice is yours, but if you start with web forms, be sure to learn about HTTP verbs, cookies, raw response flow, HTTP headers, html form / submit models Inline css vs individual files and javascript from the context of Web Forms and make sure that you know how Web Forms automates them.

Answer 2

1) Are these two technologies compatible or will MVC replace ASP.NET?

The official position of Microsoft today is that the two technologies will coexist. ASP.NET MVC will not replace classic ASP.NET. At least Microsoft will continue to ship new features to ASP.NET.

2) If I want to learn ASP.NET MVC. Do I need to learn ASP.NET as a prerequisite?

Not necessarily, but it would be better if you found out about it, because ASP.NET MVC is based on the ASP.NET core, and this will help you better understand the underlying technology.

3) Can you recommend some training resources? Book? Video? Microsoft training is not paid: (

http://asp.net/mvc is a good start.

Answer 3

This is not to say if someone is about to release another. But the easiest to learn is asp.net MVC. Pro ASP.NET MVC 3 Framework

This is a good book to study.

Answer 4

http://www.w3schools.com/aspnet/default.asp
http://aspauthors.com/aspnetbyexample/
http://www.exforsys.com/tutorials/asp.net.html

Some links that may come in handy.

Answer 5

Darin gives you good answers to 1 and 3, but I do not agree with them at 2:

2) If I want to learn ASP.NET MVC. Do I need to learn ASP.NET as a prerequisite?

Not. ASP.NET WebForms (often referred to as ASP.NET) has a VERY different paradigm.

While ASP.NET WebForms tries to hide all web pages (like POST vs. GET, HTML, how to maintain state), ASP.NET MVC depends on knowing and understanding the same thing. Learning "ServerControls" and "ViewState" for WebWebForms is of little help.

There are, of course, parts of the ASP.NET stack that you will encounter in both WebForms and MVC. Both locations use different state mechanisms (session, application, cookies, etc.), Server, Reguest and Response objects, caching mechanisms, jQuery, etc.