DevConn Highlights--Atlas
It was my first exposure to MS delivered Atlas contents. It confirmed my early impression.
- ASP.NET Script Callback is born dead, though you can still use it effectively in a number of 2.0 apps
- Ajax.NET is more lightweight and elegant I'd say. I'd go for it in any situation in which I'm building frequently used rich features
- Atlas is for the future, not meaning that it doesn't work today
- Atlas is not the MS version of Ajax; Atlas is much more
Atlas extends Ajax.NET in a number of ways.
- Browser object model to abstract away DOM differences between browsers
- Set of client-side enabled server controls, including data-binding and editable controls
- Access to server-side services through Web services (authentication, profile, session, cache)
The third point is easily replicable in Ajax.NET as well; and it probably already belongs to it in the Professional version.
I'm of course unable to see the exact future of Atlas, but I envision a perfect world in which we have one set of server controls with optional rich client capabilities. For now, we have two distinct sets which is not a bad or invalidating thing per se.
I can't say I love Atlas today, but I can't wait to see the final platform where Atlas is bringing us. Love the plan.