Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Oct 17, 2008 08:03 PM by ra00l
Nov 23, 2007 06:20 PM|LINK
Nov 24, 2007 04:31 AM|LINK
Why treat them as mutually exclusive things? Use MS AJAX for the communication layer, where it's strongest, and use YUI (or another presentational framework) for your client side chrome.
Nov 24, 2007 03:11 PM|LINK
yes, I agree with gt1329a (man, what's your name? I'm assuming it's not gt..., right? :) )
Nov 24, 2007 04:42 PM|LINK
As much as I use this user name, I should probably just change it to gt, but my name's Dave.
Nov 26, 2007 03:12 PM|LINK
I was reading we should not mix AJAX.NET and YUI library. Both libraries provides communication library. So will not able to identify the exact problem.
Nov 26, 2007 04:20 PM|LINK
I haven't had any trouble mixing ASP.NET AJAX with other AJAX frameworks that also provide communication functions. I use jQuery for presentation in almost all of my ASP.NET AJAX sites.
Nov 26, 2007 05:36 PM|LINK
Have you ever use AJAX.NET and YUI in same applicaton.
Nov 26, 2007 05:43 PM|LINK
Yeah. I didn't run into any trouble.
Nov 27, 2007 06:28 PM|LINK
Did you implement AJAX.Net and YUI on same page? I tried with one sample I was getting error in page post back. I was not able to resolve the problem.
I removed AJAX.Net from that page and application then it was working fine. Even I was reading a post on the same line. Please see the link.
Nov 28, 2007 01:39 AM|LINK
Yes. I believe I just made sure not to include the connection.js library from YUI. It wasn't necessary for the UI effects that I used. It and ASP.NET AJAX both trapping the XmlHttpRequest status changes is probably what would cause trouble using them
I've since moved on to mainly using jQuery for client side effects, so I'm not sure if more recent changes to YUI have made it harder to integrate. It should work fine though, as long as you're just using DOM effects.