Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
ASP.NET MVC Controls – Around 9 controls.
ASP.NET AJAX Controls – Around 70+ controls.
I’ve read somewhere that you cannot use AJAX controls inside ASP.NET MVC web applications. Does that mean ASP.NET MVC is less productive?
ASP.NET MVC is a very new framework compared to ASP.NET Webforms. The ASP.NET MVC framework version 2 has only been “official” for about 4 months now. Give Telerik some time to catch up. 🙂
It’s not fair to say that ASP.NET MVC is less productive than ASP.NET Webforms, but rather that there are fewer pre-built tools to serve the same functionality as those found in Webforms. That being said, due to the very lightweight and flexible nature of ASP.NET MVC you will find that a great deal of JavaScript tools and utilities are more available in MVC than they are in Webforms because there is significantly less hassle in implementing them. (F@*$ JSON with ASP.NET Webforms, thank you very much!).
jQuery and ASP.NET MVC are like peas in a pod and by combining them you will likely discover that you have access to more rich client-side functionality in MVC than you ever did in Webforms- despite the implementation requiring a little bit more JavaScript savviness than you may be used to.