We are a user experience design and software development firm
Hire us to design your site, build your application, serve billions of users and solve real problems.
We can certainly attest to the fact that combining ASP.NET with third party Ajax frameworks can have it's pitfalls. Dave Ward has put together an excellent and extensive post on his experiences integrating jQuery with ASP.NET.
Hire us to design your site, build your application, serve billions of users and solve real problems.
It does have it’s pitfalls, but it can be very rewarding when you overcome those. Using the info gathered on the article you linked to, I was able to eliminate the need for ScriptManager in my application, and the end result looks cleaner, is more consistent with the rest of the client-side code, and results in fewer requests overall. I’m quite pleased with the result!
That’s not to say that the built-in ASP.NET stuff wasn’t nice to have, it most certainly was (especially in the early stages), but the more I learn and the more the project evolves, the more I wanted this kind of consistency and control.
Comment by Takuan Daikon, Friday, June 6, 2008 @ 12:55 pm