This post originated from an RSS feed registered with .NET Buzz
by James Avery.
Original Post: Atlas - Thoughts from 2 days
Feed Title: .Avery Blog
Feed URL: /blog/Install/BlogNotConfiguredError.aspx
Feed Description: .NET and everything nice
I spent most of Monday and Tuesday trying Atlas on for size. On my current project we are working on replacing a “smart” client application with a pure web app, and our goal is to use AJAX to make this transition easier for the users. My hope was that Atlas would make these things much easier, but I don’t think it’s there just yet.
I am trying to withhold judgement because it is just a preview, but here are some of the issues I ran into:
1) I like the ability to call a web service, but it would be great to be able to markup a method on the page and call that. (like Ajax.Net)
2) I wanted to make a change to the autocomplete javascript, and I couldn’t figure out how I would do that. Where can I modify what javascript is actually emitted?
3) I tried to use the script manager and server controls in conjunction with other scripts on the same page and I could not get it to work right.
4) Declarative coding is overrated.
I like the idea of Atlas, but I don’t think it’s ready just yet. So, for now we are going to stick with Ajax.Net which handles everything I need it to. Has anyone wrapped up some of the common Ajax operations into controls using Ajax.Net yet?
(Oh, and I just have to say it. This stuff is so much easier in Ruby on Rails… if the ASP.NET team wants to impress me this stuff should be as easy in ASP.NET as it is on rails.)
Previous Topic
