Hi, yes, I will add some more documentation... but you know, time is missing always!
Regards, Michael On 5/18/06, o0JoeCool0o <[EMAIL PROTECTED]> wrote: > > I agree that things must be changed sometimes. But I think when you > make those changes it is up to you to make sure that it is well > documented. I cant find anywhere in your documentation that says > > "The syntax for calling Ajax methods has changed from the old Ajax in > Ajax Pro to include the full namespace" > > I think you should add this to your help page, tutorials and blog. > > or add a new section on the help page for Upgrading form old Ajax to > New > I only say this cause its very frustrating for someone who was using > the old to just jump to the new. The changes are simple to move from > old to new you jsut need to make people aware of them. > > #1 the web.config statement Changed > #2 the rendered Html doesnt appear to be necessary anymore > #3 Calling functions from classes need the Project name prefixed > > -Joe Cool > > > > > Michael Schwarz wrote: > > Hi o0JoeCool0o (please use realnames), > > > > yes, this is not a good step forward if we have to change a lot of > > things. Ajax.NET Professional (notice the word professional) is not a > > new version of Ajax.NET, no, it is a completly re-written Ajax > > library. The problem was that we (I and a lot of developers) are > > running web pages more than only 2 seconds, so we have to look at the > > memory problem on IE, then we need something like a cache object to > > queue requests,... > > > > I could write thousands of reasons why it was necessary to change the > > local code. Also, there are often problems when using big JavaScript > > files on web sites. Ever had the problem of having two functions with > > the same name? My web sites are using 98% JavaScript, so this is very > > hard... > > > > Maybe I have some time to show what you can do with the new way of > > source code compared with the old one. But currently I think I will > > add more features to get the best Ajax framework for .NET. (I'm > > talking about Ajax, not Web 2.0). > > > > Regards, > > Michael > > > > > > > > > > On 5/18/06, o0JoeCool0o <[EMAIL PROTECTED]> wrote: > > > > > > it took me 4 hours to find out the simplest thing last night. So I > > > thought Id make a post in hopes that a) this will be fixed to stop > > > others from having to go through the same thing and b) help people who > > > are having the issue currently. > > > > > > I was using the old Ajax.dll for 1.1, I saw the new version and wanted > > > to upgrade so I thought woohoo Ill jsut replace the dll and rename it > > > to Ajax.dll and everything would work great! Of Course this is not the > > > case. > > > > > > So first of all you need to forget you even installed the old Ajax.dll > > > jsut remove it from your project and delete it from your bin folder. > > > out with the old in with the new! > > > > > > Next you need to delete the HTTPHandlerFactory code from the web.config > > > and replace it with the new syntax. > > > > > > For 1.1 > > > <httpHandlers> > > > <add verb="POST,GET" path="ajaxpro/*.ashx" > > > type="AjaxPro.AjaxHandlerFactory, AjaxPro"/> > > > </httpHandlers> > > > > > > For 2.0 > > > <httpHandlers> > > > <add verb="POST,GET" path="ajaxpro/*.ashx" > > > type="AjaxPro.AjaxHandlerFactory, AjaxPro.2"/> > > > </httpHandlers> > > > > > > now after you do this and run it you would think hey everythign is > > > great now! right!?! > > > > > > WRONG! if you view the page source your going to see theres no <SCRIPT> > > > tags rendering in the html source like it used to, and hence you think > > > this is why you are reciving these Undefined errors from all your > > > method/function calls. If you are like me and are putting all your ajax > > > methods in its own class and not the web page you probably are doing > > > somehting like this > > > > > > myAjaxClass(doFunction, callback) > > > > > > this no longer works and this is where all the problems are. > > > > > > AjaxPro.dll only accepts calls by using the full namespace name so > > > > > > myAjaxClass(doFunction, callback) becomes > > > MyProjectName.myAjaxClass(doFunction, callback) > > > > > > POOF EVERYTHING WORKS! even without the page rendering the script html. > > > > > > I do not know why this was changed and really wish they would change it > > > to accept both methods as now I have to go back and change 30 pages of > > > code that call functions which is terrible. you should always allow > > > backwards compatibility when releasing new versions of stuff. nobody > > > wants to rewrite there entire project cause you thought of a better way > > > to do something. allow both! > > > > > > Im not trying to bash the writer of this fantastic wrapper. I am only > > > trying to save some people some headaches. This is the best Ajax > > > Wrapper out there far better then googles and I can do nothing but > > > thank Michael Schwarz for all his hard work. > > > > > > But please allow for backwards compatibility! > > > > > > > > > > > > > > > > > > > -- > > Best regards | Schöne Grüße > > Michael > > > > Microsoft MVP - Most Valuable Professional > > Microsoft MCAD - Certified Application Developer > > > > http://weblogs.asp.net/mschwarz/ > > http://www.schwarz-interactive.de/ > > mailto:[EMAIL PROTECTED] > > > > > -- Best regards | Schöne Grüße Michael Microsoft MVP - Most Valuable Professional Microsoft MCAD - Certified Application Developer http://weblogs.asp.net/mschwarz/ http://www.schwarz-interactive.de/ mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
