I have added this night some features for the Ajax.NET Wrapper DLL:

- new utility to write needed script tags (Ajax.Utility.RegisterTypeForAjax(Type t))
- the common javascript will be added when one type is registered
- Ajax.Utility.HandlerPath and Ajax.Utility.HandlerExtension, web.config must be changed by hand!!

- fixed several bugs for DataSet and DataTable
- added exception handling
- fixed return value with more than one line, special chars removed
- removed the document.title change, the Ajax.NET Wrapper will be still free for everyone!!!

- C# sample is using Ajax.Utility
- VB.NET sample now using own classes

Download new Ajax.NET Wrapper DLL: http://ajax.schwarz-interactive.de/download/ajax.zip
Download C# and VB.NET samples: http://ajax.schwarz-interactive.de/download/ajaxsample.zip

I will upload a documentation (thanks to Karl) tomorrow morning. There will we a MSDN like overview of all the classes, too.

14 Comments

• bestcomy said Wednesday, April 13, 2005 2:45:00 AM

  Well done, thanks.

• digitalghost said Wednesday, April 13, 2005 8:20:00 AM

  Some Trouble with encoding;
  When I pass a string contains chinese character from client to server
  the problem occurs .......
  how to resolve the problem ?????

• Jayaveer.B said Wednesday, April 13, 2005 9:41:00 AM

  Can i access tables with table names rather than index?

• Michael Schwarz said Wednesday, April 13, 2005 10:56:00 AM

  Unicode chars are not working at the moment. I will do this this evening...
  
  At the moment you cannot use table names instead of using the index. I will add this feature...

• Charles Chen said Wednesday, April 13, 2005 12:28:00 PM

  Just out of curiosity, are any of the browsers on Mac supported?

• Michael Schwarz said Wednesday, April 13, 2005 3:57:00 PM

  It is working with Firefox on Windows! The only thing I did not see was that the button TAG will submit the form. I will change it to a different HTML, but the Ajax.NET Wrapper is working with Firefox, Mozilla and Internet Explorer.
  
  On Mac the Safari Browser is supported (I think). I do not have a Mac to test this.

• buk said Wednesday, April 13, 2005 4:26:00 PM

  Do you have any plans to associate a license to this wrapper?

• Christoph said Wednesday, April 13, 2005 4:27:00 PM

  Hi Michael
  Yesterday, I had problems with the Wrapper. With the new version it's going fine. The Problem with the buttons do you know(preview entry)
  
  THANKS FOR THIS WRAPPER
  
  By
  Christoph

• Christoph said Wednesday, April 13, 2005 4:36:00 PM

  Is it possible to Push data from Webserver without userinput.
  e.g. update servertime every 10 Seconds
  
  thanks

• Michael Schwarz said Wednesday, April 13, 2005 6:32:00 PM

  @buk: there will be no fee at the moment for the Ajax.NET Wrapper DLL.
  
  @Christoph: I fixed some problems during the last night (11 until 4 o'clock!!!). What do you mean with the buttons problem? That Firefox issue? I will make a change to the solution this night...
  
  Yes, it is possible to "push" data from web server to the client. Currently I am working on something like events or delegates from Javascript clients. The client will iniciate a connection to the server. If the event occur on the server the result or a message will be send back. More tomorrow here on my blog!!!!

• Christoph said Wednesday, April 13, 2005 8:05:00 PM

  Hy
  Yes, the Firefox issue.
  The 10 seconds was only an example. The setTimeout could be a solution. I'll wait until you've done the events/delegates.
  
  by
  Christoph

• digitalghost said Thursday, April 14, 2005 2:00:00 AM

  Will you associate a license to this wrapper in the future?
  can I use it in a commerce project???

• Michael Schwarz said Thursday, April 14, 2005 5:21:00 AM

  Everybody can use this free Ajax.NET Wrapper DLL. You can use the DLL in any project you want. You cannot resale this but you can deploy it with your projects.

• Andrew Cupper said Monday, April 18, 2005 1:18:00 PM

  This is really neat. It would be nice if you could extend the JavascriptMethod attribute to indicate if session state is required (like the web service WebMethod attribute). The PageHandlerFactory would need to check the attributes of the method being called and return a PageHandler marked with IRequiresSessionState if session state is required, (eg. PageWithSessionHandler which derives from PageHandler).