Is ASP.Net Server Control, Postback Architecture failed in current Web 2.0 World [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 6 years ago.

开发者_StackOverflow Improve this question

What i am looking around me is the drastically change in ASP.Net Architecture. More and more company are following the approach of

JSON based wcf service in middle tier. Plain HTML based UI tier with JQuery/Ajax.

No Postback at all, This contradicts the Default behaviour of Asp.Net Server Control/Code Behind Event handler/Postback. I am a Asp.Net Web Developer for around 4 years, and concerned about the future of ASP.Net.

Is the Default Architecture of ASP.Net is Outdated at all? Does MVC or ASP.Net 4.0 Tries to solve the Issue?

---

Failed is a bit strong a word for ASP.NET. Flawed is probably a better word. MVC certainly addresses the issues that you have raised. And more. Yes the default architecture of ASP.NET is now outdated. The fact that ASP.NET MVC sits on top of ASP.NET means that you can still use the productivity enhancing features of ASP.Net and any legacy code that you have in ASP.Net until the point where you are able to author your site in MVC quicker than you can in ASP.NET. This will happen very quickly.