MSDN Roadshow Session 1 - ADO.NEXT – Entity Framework & Data Services

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    MSDN Roadshow Session 1 - ADO.NEXT – Entity Framework & Data Services - Presentation Transcript

    1.  
    2.  
    3. Eric Nelson Developer & Platform Group Microsoft Ltd [email_address] http://blogs.msdn.com/ericnel http://twitter.com/ericnel
      • Relational
        • Improved
          • XML
          • UDTs
        • New
          • Filestream
          • Hierarchy ID
          • Date & Time
          • Spatial data
          • Sparse columns and wide tables
          • Filtered indexes
          • Change tracking
          • Table parameters to SP calls
          • Resource governor
          • SP control and monitoring
          • Database compression
          • Declarative management
          • ...
      • SQL Server Integration Services
        • VSTA replaces VSA
        • ADO.NET
        • Performance
        • Merge
        • ...
      • Reporting Services
        • “ IIS free”
        • Tablix
        • New designer
        • ...
      • BI
        • Cube design
        • Design alerts
        • Performance
        • ...
    4.  
    5.  
      • What is it?
        • Technique for working with relational tables as if they were objects in memory
        • Intention is to hide away the complexity of the underlying tables and give a uniform way of working with data
      • Why use it?
        • Productivity
        • Retain database independence
      • Notes
        • There are many ORMs for .NET developers already in existence. E.g.
          • LLBLGen Pro http://www.llblgen.com/
          • Nhibernate http://www.hibernate.org/343.html
          • EntitySpaces http://www.entityspaces.net/Portal/Default.aspx
        • Objects vs Classes vs Entities
    6.  
      • What is it?
        • Tools and services to create an Entity Data Model
          • EDM gives ORM to SQL Server, Oracle, DB2 etc
        • Tools and services for consuming an Entity Data Model
      • Why use it?
        • Productivity
        • Complex mapping between entities and database tables
        • Works great with ADO.NET Data Services
      • Notes
        • Strategic but just released...
      • Application model
        • Mapped to a persistence store
      • Comprised of three layers:
        • Conceptual (CSDL)
        • Mapping (MSL)
        • Storage (SSDL)
      • Database agnostic
      • Comprised of:
        • Entities
        • Associations
        • Functions
      Conceptual Mapping Storage Entity Data Model
    7.  
      • Entity Client
        • Entity SQL
      • Object Services
        • Entity SQL
        • LINQ To Entities
      • Familiar ADO.NET object model:
        • EntityCommand
        • EntityConnection
        • EntityDataReader
        • EntityParameter
        • EntityTransaction
      • Text-based results
      • Read-only
      • Uses Entity SQL
      • Queries materialized as Objects
        • ObjectContext
        • ObjectQuery<T>
      • Built on top of Entity Client
      • Two query options:
        • Entity SQL
        • LINQ
      • Runtime services:
        • Unit of work
        • Identity tracking
        • Eager/explicit loading
    8. LINQ To Entities Object Services Entity SQL Entity Client ADO.NET Provider
    9.  
    10. Vendor DB Support Microsoft SQL Server Oracle Sample, Generic Sample Devart Oracle, MySQL, Postgress Phoenix SQLite Sybase SQLAnywhere Npgsql PostgreSQL IBM DB2, Informix Dynamic Server MySQL AB MySQL OpenLink Many via OpenLink ODBC or JDBC DataDirect Oracle, Sybase, SQL Server, DB2 Firebird Firebird
    11. LINQ to SQL LINQ to Entities Database Support SQL Server Many Object Relational Mapping Capabilities Simple Complex Requires Attributed .NET Code No Yes Status Released Just Released 
      • LINQ to SQL
        • var products = from prod in db.Product
        • where prod.Color == &quot;Blue&quot;
        • select prod;
      • LINQ to Entities
        • var products = from prod in db.Product
        • where prod.Color == &quot;Blue&quot;
        • select prod;
      • In general – LINQ to Entities does more – but not always!
      • Only migration that will ever happen is LINQ to SQL migration to LINQ to Entities
    12.  
      • What is it?
        • HTTP access to an object model exposed as RESTful Web Services
        • Data and/or methods
        • Data returned using ATOM or JSON
        • Read/Write
      • Why use it?
        • Easy to expose data over the internet/intranet accessible by any client
    13. Data Access Layer Entity Framework Relational database Other sources Data Services Runtime Hosting/HTTP Listener Custom IQueryable/IEnumerable [+ IUpdatable] HTTP
    14. Resources Res 1 Res 2 Res 3 Res 4 HTTP Request URL VERB Payload HTTP Response Status GET POST PUT DELETE XML JSON Payload XML JSON
      • 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* )
    15.  
    16.  
      • http:// blogs.msdn.com/ UKDevEvents
        • Post event resources for all Microsoft UK developer focused sessions
      • The team
        • Eric Nelson http://blogs.msdn.com/ericnel
        • Mike Ormond http://blogs.msdn.com/mikeormond
        • Mike Taulty http://mtaulty.com
    17.  
    18.  
    19.  
    20. Entity Data Model SSDL SQL Oracle Other SSDL HTTP Entity Client CSDL MSL Object Services ESQL “ select o from orders” LINQ to Entities “ from o in orders...” ADO.NET Data services Provider Provider Provider SSDL Custom Interceptors (Query, Update) Service Operations (Methods) Entity Data Model
      • RE presentational S tate T ransfer
        • 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”?

    + ukdpeukdpe, 12 months ago

    custom

    1251 views, 0 favs, 0 embeds more stats

    Did you miss the opportunity to attend the MSDN Roa more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 1251
      • 1251 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 53
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories