I talked today with a Intel developer and he showed me where the are using Ajax.NET Professional JSON Library. The Intel Software Developer Network has it's own video library where you can see great videos on several technologies Intel is offering with it's processors. We talked about why they are using AjaxPro and the answer (that I get more and more) is: "we are using Microsoft .NET Framework 1.1". I'm happy to see that the decission to support .NET 1.1 in all my releases was one of the biggest benefits you get when using AjaxPro. Well, Intel talked about using AjaxPro as AJAX library, too. So, maybe we will see more web applications from Intel next time.

Another talk with a big company in India ended with the same results. The created a small library that should do the same work, but when put the web application online they got a lot of feedback that the web application was only working with Internet Explorer 6. Because they already seperated everything in own classes and methods moving to AjaxPro was very easy. About 2 hours work and the web application was running with all common web browsers that support JavaScript and XmlHttpRequest (or IFrame when it is disabled).

On my last German INETA talks we had similar discussion about the main problem most companies have today: they are still using .NET 1.1 or want to add AJAX features to existing web applications which cannot be converted in shortly time.

2 Comments

• airoc said Sunday, April 8, 2007 6:50:20 AM

  hi,hope you can get this message. i've got a question for you , you have compiled all the stuffs including xmlHTTPrequest into ajaxpro.dll , but how can i get the xmlHTTP.readyState ? when my site is working sometimes the asynchronous function failed to process data , i mean maybe the xmlHTTP.readyState is not ready. i want to catch this and do something to tell user that data process failed. please enlighten me , thx !

• Wallym said Monday, April 9, 2007 2:15:49 PM

  Congrats Michael. When I have someone ask about AJAX on ASP.NET 1.1, I am always sending them to the AJAX.NET Pro Library. :-)