Actully, I'm starting to think that Michael did a lot of extending of current .Net technologies. I applaud him for his hard work and I appreciate it, but how much of it is really neccessary?
For instance, at least in .Net 2.0, you can specify methods in your code behind as [WebMethods] like you would in a web service, and make it directly accessible like with [AjaxPro.AjaxMethod] fully qulaified the .net is: [System.Web.Services.WebMethod] You can also use callbacks with certain .net controls such as the treview, gridview etc. These callback events are non-postback calls between client side and server side code. I'm not a big fan of ATLAS, yet (it is still CTP), but it does have some cool features that let you do many of the things you need. All of this is .net framework built-in functionality that lets you get certain .net control specific ajax functionality right out of the box. I like this because it keeps you in one contiguous framework that is built by and supported by a large group of experienced developers (Microsoft) and keeps you technology usage in your site more fluid. In all honesty, I think AjaxPro was the bomb for pre .Net 2.0 days and did what MS failed to bring to the table. However now that they are catching up with current trends, which they are always slow to do, we have better frameworks to use to accomplish Web 2.0 tasks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info/ Don't forget to read my blog at http://weblogs.asp.net/mschwarz/ -~----------~----~----~----~------~----~------~--~---
