The document discusses ADO.NET Data Services and the Entity Framework. It provides an overview of ADO.NET Data Services, explaining that it allows data to be consumed over HTTP using RESTful services. It also discusses key concepts like REST and exposing data sources. The document then covers the Entity Framework, an object-relational mapper that abstracts the database schema and allows mapping objects to relational data. It provides examples of using the Entity Framework object model to perform queries and access data.

1. ADO.NET Data Services&Entity FrameworkDiana NemeşuSeptember 20091

2. Agenda2Telemon Project

3. Intro ADO.NET Data Services: - Why? - How?ADO.NET Entity Framework

4. DemoTelemon Project3Purpose: to build a platform for e-health, namely a platform for Telemonitoring "anywhere and anytime”, in real time;Parameters monitored: ECG, Resp, Temp, Acc, SPO2, Blood pressureTechnologies: - DB: SQLite, SQL Express; - ADO.NET / ADO.NET Data Services; - WinForms, DevExpress

5. Telemon Overview4Sensor1Sensor2Device(SmartPhone)Server TelemonDoctor ApplicationTelemonDataBaseTelemon Services

6. Device Application5

7. Doctors Application6

8. ADO.NET Data Services “Astoria”http://astoria.mslivelabs.com/ 7

9. Why?8Provides an API that allows data to be created and consumed over HTTP using RESTful service. Supports all database operations using URI. Can expose an entity model via an URI. Is RESTful service to support CRUD operations on database. Could be consumed by any type of client like Windows, Silverlight, Web , AJAX and console.

10. How?9Data is sent over HTTP in both directions;Defines a hosting interface IDataServiceHost that abstracts its implementation from a specific host (WCF, ASP.NET, IIS); Server operations: - static layer that implements URL translation - data source being surfaced to the data service.

11. Concepts10REST: - focuses on key components that enable easy integration and interaction with other systems; - approaches the need for interoperability and communication between systems through separation of layers; - Yahoo, Facebook, Flickr, Amazon, Google, ebay, digg;

12. 11The ADO.NET Data Services framework provides patterns and libraries that enable the creation and consumption of data driven services for the web;Expose Data Source to Data Service:- Entity Framework - LINQ to SQL - Surfacing custom data sources using CLR classes - Creating a custom IQueryable<T> provider to surface a custom data sourceOffline-Enabled Data Services (Astoria Offline)

13. System Requirements12Microsoft .NET Framework 3.5 SP1 Visual Studio 2008 SP1ADO.NET Data-access providers (Microsoft SQL Server 2005)

14. ADO.NET Entity Framework13IntroductionADO.NET ProvidersEntity Data Model (EDM)MappingDatabase Schema vs Conceptual SchemaUsing Object Modelhttp://msdn.microsoft.com/en-us/library/aa697427(VS.80).aspx

15. Introduction to Entity Framework14Is a set of data access APIs for the Microsoft .NET Framework;Version 1 was included with .NET Framework 3.5 SP1 and Visual Studio 2008 SP1; version 4.0 is available in Beta form as part of Visual Studio 2010;Abstracts the relational(logical) schema of the data that is stored in a database and presents its conceptual schema to the application;

16. 15ADO.NET Providers: Connector/Net(MySQL), DB2.NET, dotConnect, Oracle Data Provider for .NET, DataDirect Connect for ADO.NET, Npgsql;EDM: - specifies the conceptual model of the data via the Entity-Relationship data model; - the EDM schema is expressed in the Schema Definition Language (XML format);Mapping: a 1:1 (one to one) mapping is generated between the database schema and the conceptual schema;

17. Conceptual SchemaDatabase Schema 16

18. Using Object Model 17using(telemonEntities DB=new telemonEntities()) {foreach (User user in DB.User) {Console.WriteLine("User{0} ** Username{1}",user.Id,user.Username); }foreach (Alarmealarma in DB.Alarme) {Console.WriteLine( "Alarm: {0} ** Username: {1} ** Session: {2}",alarma.Id,alarma.User.Username,alarma.PacientSession.Name); }ObjectQuery<SignalData> signals = DB.SignalData;IQueryable<SignalData> signalList = from s in signals select s;foreach (SignalData signal in signalList {Console.WriteLine("Signal{0} ** Session{1} ** Username{2}",signal.Id,signal.PacientSession.Name,signal.PacientSession.User.Username); }

19. Demo18

20. 19ADO.NET Data ServicesQuestionsDiana Nemeşudin@rms.rodyana0106@yahoo.com