In one of my previous posts I have told you about ADO.NET - Astoria and Jasper from MIX07.Now you can download it - For those who played with LINQ here's the next phase : Microsoft Codename "Astoria" - May 2007 Community Technology Preview, along with Jasper MIX 2007 CTP so you could realy do something real for the community , like EntLib Contrib project - Start Coding NOW!
EntLib Contrib is a community-developed library of extensions to the patterns & practices Enterprise Library, while next phase,which is comming later this week ,is Web Client Software Factory Contrib and Smart Client Software Factory Contrib. Now is YOUR chance to extend well known Libraries !
for more info:
About p&p "Contrib" projects
Guidelines for EntLib Contrib code
Sign Up Process
... waiting for the EntLib 4.0 , "The Community Version" ;)
BTW: Tom Hollander, is leaving the team :(
Here's the link for the
download version of the keynote by Ray Ozzie and Scott Guthrie Keynote.
don't forget that you can both browse the
www.visitmix.com library, as well as the
http://sessions.visitmix.com/default.asp to download the videos for offline viewing [ AND THERE'S LOOOOTTTTSS OF THEM :D ]
It seems that the ADO.NET team has/going ( i'm not in LV ) to announce two on going projects which for all you LINQ enthusiastic people - if LINQ / DLINQ / XLINQ wasn't enough , here's another pile of paper work you'll have to read about [ that is if ADO.NET is your thing ;-) ].
Technology NO.1 is code name "Astoria" : "The goal of Microsoft Codename "Astoria" is to enable applications to expose data as a data service that can be consumed by web clients within a corporate network and across the internet.", or in plain english LINQ with partial WCF capabilities.
Check out the Astoria webpage at http://astoria.mslivelabs.com for more information and a link to the CTP download.
Pablo Castro has published this document which introduces the concepts and motivations for Astoria.
Technology NO.2 is code name "Jasper". Jasper seems to be like the level you'd get after SP2 of LINQ, why ?
Because "Jasper" uses a set of new technologies to make this happen:
- Dynamic generation of data classes so there is no configuration or design time code-gen to carry around.
- Rich query and O/R capabilities because "Jasper" is built on top of the Entity Framework.
- Auto-binding capabilities for ASP.NET, WinForms, and WPF to make binding data to a UI simple and automatic.