Wednesday, November 22. 2006Migrating from Atlas to ASP.NET AJAX
This blog entry serves as a kind of TOC for a series of entries I will be doing during the next days and weeks. I am currently porting several apps (and yes, book samples) from Atlas to ASP.NET AJAX, and from time to time I have a kind of "gotcha!" experience. When this is the case, I will write a short blog entry on it. I know that Microsoft provided some documentation for the migration, but many readers wrote me that they were not too happy with it and/or are missing content.
All entries will be linked here, so if you are reading this blog using a feed reader, please do not worry when this entry here changes from time to time ... 
|
Calendar
QuicksearchArchivesSyndicate This BlogCategoriesFriendly BlogsPowered by
Blog Administration |
|||||||||||||||||||||||||||||||||||||||||||||||||
The most fundamental change when working with (local) web services with ASP.NET AJAX in contrast to Atlas is that the WebService attribute is not supported in this scenario. So when ASP.NET AJAX is trying to call the JavaScript proxy (by loading File.asmx
Tracked: Nov 22, 17:16
I have always had my beef with the client controls Atlas introduced. I am using JavaScript since approximately ten years now, so I know my way around DOM fairly well. So why add another layer in between? Of course there are scenarios where that makes sens
Tracked: Nov 28, 14:06