Alber Weinert [1] is talking [2] about Ajax.NET Professional [3] (and details on JSON [4]) in Cologne, Germany:
Posted by Michael Schwarz on Wednesday, July 19, 2006
I removed addNamespace because of the missing support on older web browsers or mobile devices. The problem is that addNamespace will add a new property to the window object. This is working great on all common web browsers. See the next lines to see how you can change addNamespace usage to get your JavaScript working on all web browsers.
Posted by Michael Schwarz on Tuesday, July 18, 2006
Yesterday night I build an example on how to use Yahoo! Web Services [1] with the AjaxPro JSON parser [2]. The example will call a Yahoo! Web Service with output type set to JSON (see http://developer.yahoo.com/common/json.html [3]). The response will be deserialized to an .NET structure using the AjaxPro JSON parser (from the stand-alone version or the build-in parser in Ajax.NET Professional).
Posted by Michael Schwarz on Tuesday, July 11, 2006
There is a new stand-alone version for JSON [1] serialization/deserialization library available for Microsoft .NET 1.1/2.0. The JSON parser is extracted from my Ajax.NET Professional [2] library and will be available in the download package in the future. Download the new version at http://www.ajaxpro.info/ [2] (see the new link for the stand-alone version).
Posted by Michael Schwarz on Monday, July 10, 2006
As there was a little discussion [1] about serialization of .NET types and deserialization of these genereted JSON strings I have updated Ajax.NET Professional [2] (version 6.7.9.1) to allow parsing of new Date statements, too. You can use the JSON generated string to do a deserialization right after, now.
Posted by Michael Schwarz on Monday, July 10, 2006
Because I'm currently playing with a lot of AJAX frameworks I'm searching for the correct use of dates and times in web applications. Ajax.NET Professional [1] is using time zone indentifier to know from which time zone the request is comming from. See following server-side C# code:
Posted by Michael Schwarz on Friday, July 7, 2006
Ajax.NET Professional [1] is using attributes, there is no need to inherit from special pages or include dummy web controls to do all the job, there is no need to write special source code. Any .NET assembly can include classes with AjaxMethods that can be used in your ASP.NET web application.
Posted by Michael Schwarz on Friday, July 7, 2006
I read the post from Scott Hanselman [1] today comparing the internal use of JSON de-/serializer from the Atlas framework [2] and Ajax.NET Professional [3].
Posted by Michael Schwarz on Wednesday, July 5, 2006
Today I found something interesting when using different security in Internet Explorer settings. If Binary and script behaviors is disabled in internet sercurity settings Google talk user images are not displayed. Hm, didn't know that Internet Explorer settings will change user expierience of Google talk.
Posted by Michael Schwarz on Monday, July 3, 2006
In Internet Explorer (and all other common web browsers) you have an menu item File -> Work off-line. What does this do with you web application? Of course, it is working offline, no communication possible to the web server. When connected with a dial-up connection it can happen that this is done automatically if you disconnect from your internet service provider.
Posted by Michael Schwarz on Monday, July 3, 2006
This weekend I had a deep look on the native XMLHttpRequest support with the new Internet Explorer version 7 which is still in beta. If you do a Google search for "native xmlhttp support ie [1]" you will read that everyone is happy with this native support. Yes, it is the first step to have XMLHttpRequest on every PC. Ajax developers have changed their JavaScript source code to support this new object, this is great!
Posted by Michael Schwarz on Monday, July 3, 2006