New demo added and some bugfixes.
Changes since last release, which was 2.0.001:
posted by Troels Wittrup at 2:45 AM
Troels lives in Espergærde (Denmark). He co-organizes meetups like BarCamp Copenhagen and LastFriday. His blog is about pushing the boundaries of C#.
Everything you find here is free for private and educational use, as long as you credit the author and you don't remove any copyright notices. Contact Troels Wittrup Jensen if you have any questions.
The information provided comes without any warranty whatsoever. Use it at your own risk. All the other standard disclaimers also apply.
A blog for C# and ASP.NET developers.
6 Comments:
Hey, I really like your Ajax approach. However, Version 2.x is not working for me. It seems the problem is in the javascript axd. When OutPost tries to import Outpost.axd/Ajax.js it fails to do so saying that the resource does not exist. I tried v1.6 and the resource Outpost imports is called Outpost.axd/Js This respurce is found and it works like a charm. I'm using .NET 2.0. I hope my error report helps. If you need more information about the problem just write back (mariodivece@yahoo.com)
Is there a way (i.e. a javascript variable) to check whether the call has finished and get the status of the call? It would be useful because otherwise, when the user, say, clicks a button and nothing happens during the roundtrip, might create confusion about the functionality of the page. If instead, through javascript, we could check for the status of the call, one could customize how this "in progress" feedback is given to the client.
Hi Mario, I hope you solved the problem with the "resource does not exist" earlier. I guess it is because I renamed the resource from "Js" to "Ajax.js" in order to enable script debugging.
Regarding the way to implement a progress indicator, I will make it as a new feature in the next release (coming soon!) and put in a demo of that as well.
Hello, first of all I want to thank you for this framework, makes enhancing webpages with AJAX functionality a breeze. I do have a question though. Is .NET 1.1 no longer supported for Outpost 2.0+?
The code is not compilable in .NET 1.1, seems the code in html.cs uses some generic collection classes?
i like your blog ....
Your blog is very nice
Post a Comment
<< Home