210 likes | 319 Views
ADO.NE X T Advances in Data Access for 2008. Mike Taulty Developer & Platform Group Microsoft Ltd Mike.Taulty@microsoft.com http://miketaulty.com. What’s Coming in ADO.NET?. Slated for Summer, 2008 as part of an update to VS 2008 and Framework V3.5
E N D
ADO.NEXTAdvances in Data Access for 2008 Mike Taulty Developer & Platform Group Microsoft Ltd Mike.Taulty@microsoft.com http://miketaulty.com
What’s Coming in ADO.NET? • Slated for Summer, 2008 as part of an update to VS 2008 and Framework V3.5 • Current bits are packaged in ASP.NET 3.5 Extensions Preview • More about that package in the next session
Entity Framework – Key Facts • Extends the ADO.NET Provider Model • Pluggable to support any database • Functionality • Abstracts a model from your store schema • ADO.NET API or LINQ-enabled ORM • Status • Currently at Beta 3
Provider Specific (PL/SQL) “SELECT * FROM CUSTOMERS” ADO.NET Today App Code ADO.NET Command Providers Execute SQL Server DataReader Oracle Oracle Customers Customers Customers ...
ADO.NET Entity Framework Conceptual Model Map Customers UKCustomer UKPremiumCustomer
Provider Agnostic (ESQL) “SELECT * FROM UKCUSTOMER” ADO.NET Entity Framework App Code ADO.NET Conceptual Model Map Entity Provider Command Execute DataReader UKCustomer UKCustomer UKPremiumCustomer Customers UKCustomer Providers* SQL Server Oracle Oracle ...
ADO.NET Entity Framework EF EF .NET Entity Provider (Entity SQL) Programming Model EF Entity Data Model (CSDL) Conceptual Model LINQ Reader Connection Command Entity Entity Object Relational Mapping relationship Mapping (MSL) V2.0 Store Model (SSDL) .NET Data Provider Store Reader Connection Adapter Command
{ Entity Framework } demo
Data Services – Key Facts • Extends Windows Communication Foundation V3.5 • Functionality • CRUD access to data over RESTful web services • Built-in URI-based query syntax • Client-side libraries for .NET and AJAX clients • Status • Currently in CTP ( latest December )
RESTful Web Services? Resources HTTP Request Res 1 URL GET Res 2 VERB POST Payload PUT Res 3 JSON JSON XML XML DELETE Res 4 HTTP Response Status Payload
RESTful? • REpresentationalState Transfer • Server-side resources identified by a URI • Access is over HTTP, verb tied to action • GET to read the value of a resource • POST to create a new resource • PUT to update an existing resource • DELETE to delete a resource • Returned data is “plain” – XML or JSON • Is this “the death of SOAP”?
data? what kind of data? • Provide a type with public properties which are; • IQueryable<T>, IEnumerable<T> • Also get write access if your type implements; • IUpdatable • Works well with generated code from; • ADO.NET Entity Framework (ObjectContext) • LINQ to SQL (DataContext*)
{ Data Services } demo
What’s Coming in ADO.NET? • Slated for Summer, 2008 as part of an update to VS 2008 and Framework V3.5 • Current bits ASP.NET 3.5 Extensions Preview
Resources http://www.msdnroadshow.co.uk