For those of you who have already put your feet into the waters of .NET 3.5 SP1, you have probably seen some amazing things with ADO.NET Data Services coupled to the Entity Framework. But that coupling may lead to blindness. Allow me to explain.
[continue to article: Images as a Service with ADO.NET Data Services]
I just finished watching Pete Lacey talking about REST and web services for the past 30 minutes or so. As I am invested in "Astoria" (now ADO.NET Data Services), I've gotten into Atom, Atom Pub, HTTP and REST a lot more, but a lot of it still didn't 'really click' until I watched that.
If you have some idea about Astoria (from Microsoft), or REST, and you want to have someone put all those pieces in your head together to make a beautiful puzzel painting... watch that video.
Some of my favorite highlights from that video... [full post]
I just finished an article on my favorite new topic, ADO.NET Data Services... There's not a sample download at the end (like their normally is) because of it being in beta, and I'm pretty tired, so it might not sound great... let me know what you think. Here's the URL: http://www.singingeels.com/Articles/ADONET_Data_Services__AJAX_Tree_View.aspx
I've been getting into ADO.NET Data Services (code name "Astoria"), and there is a great question about how you think it will be used the most... I said my peace, don't be shy! If you're the kind of person who complains after a launch that Microsoft is missing something, then now's your chance to give your voice *before* it goes live!
http://lostintangent.com/2008/05/05/which-data-service-client-environment-is-most-compelling-to-you/
Thanks,
-Timothy