CODEWITHSUNDEEP
.netasp.netasp.net-ajaxasp.net-4.0
Matías Fidemraizer
Matías Fidemraizer

Reputation: 64943

Is ASP.NET AJAX for script controls obsolete too?

I've been developing some script controls in server-side with their client-side counterpart.

Since I've found some articles and Stakoverflow questions regarding that Microsoft has practically deprecated ASP.NET AJAX Client Library in favor of jQuery, I'm worried about if developing script controls is also obsolete.

I find useful OOP Microsoft AJAX's API and its integration with server controls.

Finally, I'm currently using ASP.NET 4.0.

Thank you in advance.

CONCLUSION:

*My project is using ScriptControls and Callback API. Inside ScriptControls I've been always using jQuery instead of AJAX Client Library. In other words, I believe that I don't have a hard dependency on what's meant to be obsolete in .NET future versions.

Current scenario is .NET 5.0 is far enough and current version, 4.0, has these ASP.NET features and, for now, there are the official approaches provided by ASP.NET.

Since .NET 4.0 will be in the market as the latest version for some time yet, and I doubt Microsoft could completely remove ASP.NET AJAX 4.0 features in 5.0, I believe both ScriptControls and Callbacks will be safe for the next 5 years, and this is enough for me.

Correct me if I'm wrong, but ScriptControls+Callback API+jQuery (for DOM manipulation) should be safe and a good way for the medium/long run.*

Upvotes: 1

Views: 1515

Answers (2)

Roopesh Shenoy
Roopesh Shenoy

Reputation: 3447

Yes, in all fairness, JQuery is the way forward now. For existing projects, it can be pretty painful to make the shift, and if things work well as they are, I don't see why it needs to be changed anyways.

But if you are starting anything new, and if it is going to survive for a while (as all software does), then you are better off with JQuery, since it will keep evolving over time and you can keep reaping those benefits.

Plus if there was ever a time to learn JQuery, it's now. Might as well dive head-on.

Upvotes: 2

Russ Cam
Russ Cam

Reputation: 125498

Well, Microsoft stopped supporting LINQ to SQL a long time ago in favour of Entity Framework but people are still using LINQ to SQL.

Whilst it is true that Microsoft is no longer putting effort into developing MS AJAX library any further, the judgment call for me on whether to use it or not is if the target developers know it better than another JavaScript library (assuming that time to get things done is an important factor).

If you're starting from an equal standpoint, I'd probably go with jQuery because it's supported by Microsoft and there is a large community that can help with issues, it's under continuous active development and it will help if you decided to move parts of the application to ASP.NET MVC, which plays very nicely with jQuery.

Upvotes: 1

Related Questions