views:

122

answers:

6

Hi All,

I know this is a duplicate kind of question. I have worked with ASP.Net and ASP.Net MVC 1.0. I never really got a chance to get into ASP.Net AJAX.

My question is it really worth to invest in learning ASP.Net AJAX 3.5 or 4.0 given the fact, I have hardly used it ?

Please let me know your advise.

EDIT : - Thanks all for your response. Robert\Justin\etc have provided valuable insight.

I have a copy of ASP.Net AJAX In Action in my office library. My guess this book should be pretty enough for me, though It was for ASP.Net 2.0. Do I need to invest in books\Time for ASP.Net AJAX 3.5 or 4.0 ?

+2  A: 

Are you interested in it? Do you think you might want to use it someday for something? Do you want to make sure you're equipped to use the best tools for the problem at hand?

If you answered yes (to any of them), you should invest the time to learn it.

You can never hurt yourself by learning new things (as long as you learn how to properly apply them).

Justin Niessner
+2  A: 

ASP.Net AJAX is probably not worth learning if you're going to stick with Asp.Net MVC going forward. Or to put it another way... You can spend your time and resources learning something else.

It's not that it's a bad framework, it's good. But it's designed to make javascript familiar to .Net Developers who are used to the Webforms model.

I suspect that MS has de-emphasized the role asp.net Ajax will play in the future.

Atømix
+2  A: 

ASP.net ajax is a pretty terrible library, compared to the alternatives. The only reason to use it is if you are using the asp.net ajax controls.

Matt Briggs
It's not terrible in that it was designed to make javascript familiar to Webforms developers. In that sense, it succeeds.
Atømix
well, functionally, it is a lot bigger then other libraries that do the same things, only better. Style-wise its pretty bad too, although you could say that is a plus if people want to write javascript in the same style as a C-like language. The question was if he should learn it or not. If he is using mvc, there are other better alternatives, if it is an 'expand your mind' type thing, other libraries that approach the problems in ways that are closer to idiomatic javascript are a better choice.
Matt Briggs
as an aside, I would apply the second point to prototype as well, only it makes javascript more like ruby. IMO when you are writing javascript, you should play to the strengths of the language, not try to force it to be something it isn't.
Matt Briggs
+1  A: 

Yes. Learn as much as you can as often as you can. While you may never use these skiils directly, the experience and breadth of knowledge will help you in any situation.

etc
@etc : Your answer definitely makes sense.
Yogendra
That is a nice mantra to go by, however, but you have to stay pragmatic and learn what you need without waisting too much time.
Diego C.
+10  A: 

There are so many Ajax Libraries out there, is not even funny. Here is a good link on what is out there.

Since we already use ASP.net, I made sure to spend a little bit of time familiarizing myself with asp.net ajax. Just enough to do the basics. However, for everything else, we use jQuery, which, by the way, integrates nicely with ASP.Net. Have you ever wondered why the ASP.Net team has started supporting jQuery: intellisense, included scripts, contributing to the project, doing demos with it, etc...

So here is my 2 cents. Look into the basics in asp.net ajax but focus your efforts into, IMHO, a better library like jQuery.

Good luck! -D

Diego C.
Very well put Diego :)
HasanGursoy
A: 

If you have an understanding of ASP.NET already, I'm assuming you also understand JavaScript and etc. As a result, AJAX wouldn't buy you that much (unless you're on a project that requires knowing it). If you plan on being a web developer for any length of time, I would say that Silverlight and/or jQuery would be much more valuable than Ajax.

Nate Noonen
if you mention Silverlight, you might as well mention Flash or JAVA... because it needs a plugin to run.jQuery is pure Javascript include and is very AJAX oriented.
BerggreenDK
I was commenting on products that will enhance dev experience going forward. Silverlight is plugin based, but at least it's not Java. And Flash is almost dead.
Nate Noonen