Building nTier Applications with Entity Framework Services (Part 1)
Download as PPTX, PDF1 like999 views
The document discusses building n-tier applications using the Entity Framework, emphasizing its architecture and the advantages of Object-Relational Mapping (ORM). Key features include lazy loading, model-first approach, and various resources for learning and improving productivity. It also highlights local user groups and offers opportunities to win software prizes for attendees.
Building nTier Applications with Entity Framework Services (Part 1)
- 1. Building nTier Applications with Entity Framework ServicesPart 1
- 3. Check Out Your Local User Groups!San Diego Cloud Computing User Groupwww.azureusergroup.com/group/sandiegoazureusergroupSan Diego .NET Developers Groupwww.sddotnetdg.orgSan Diego .NET User Groupwww.sandiegodotnet.comSan Diego SQL Server User Groupwww.sdsqlug.org
- 4. Win Free Software!RulesProvide your business card (or email and name)*Indicate on the back what software you are interested inOtherwise I will pick Winners will be picked next week*Yes, most likely I’m going to send you and email about my user group (sddotnetdg.org) and or web site (dotNetTips.com)PrizesCodeRush and Refactor Pro from DevExpress (4)SecondCopy (automatic backup software) (5) *CodeIt.Right Standard from SubMain (4)*Requires mailing address and phone number
- 5. Agenda
- 6. Overview
- 7. nTier Architecture OverviewModel to create flexible reusable applicationsOnly need to modify or add layers instead of rewriting entire applications over
- 8. User ExperienceSecurityActive Directory, Card Space, Windows Identity FoundationUI ComponentsWindows Forms, Windows Presentation Foundation, ASP.NET (AJAX, MVC), Silverlight, Windows MobilePresentation LayerLocal Storage/ CacheCommunications LayerWindows Communication Foundation (WCF), WCF Data Services, Web Services, Sync Services, Azure (Cloud), RIA Services, Workflow ServicesBusiness LayerBusiness EntitiesT4 TemplatesBusiness ComponentsBusiness WorkflowWindows Workflow FoundationData LayerEntity Framework, LINQ to SQL, DataSetsSQL Server
- 10. Object Relational MappingWhat is ORM?Technique for working with relational tables as if they were objects in memoryIntention is to hide away the complexity of the underlying tables and give a uniform way of working with dataWhy use ORM?ProductivityRetain database independenceObjectsClassesEntities
- 11. Object Relational MappingIt’s nothing new, just new to .NETThere are many ORMs for .NET developers already in existence. E.g.LLBLGen Pro http://www.llblgen.com/Nhibernate http://www.hibernate.org/343.htmlEntitySpaces http://www.entityspaces.net/Portal/Default.aspx
- 12. The Microsoft Entity Data ModelAn extended relational model with Entity-Relationship Model conceptsEntity TypesStrong type with IdentityInheritanceScalar/Complex propertiesEntitySetsHold instances of Entity TypesSimilar to relational tablesCan have multiple Entitysets of the same EntityTypesRelationships ("Associations")Named relationships between Entities0..1:*, 0..1:0..1, 1:1, 1:M, M:NNavigation may be exposed as NavigationProperties on EntityTypesAssociationSetsContains instances of associationsMay be queried directlyEntityContainersContains EntitySets, AssociationSetsSalesPersonEmployeeID = 294272LoginID = adamTitle = "Dev Lead"VacationHours = 0…Manager11NReportsSalesPersonSalesPersonEmployeeID = 729742LoginID = peteTitle = "Developer"VacationHours = 0…ExpenseAccount = …CarLicenseNum = ……SalesPersonEmployeeID = 729742LoginID = peteTitle = "Developer"VacationHours = 0…ExpenseAccount = …CarLicenseNum = ……EmployeeID = 729742LoginID = peteTitle = "Developer"VacationHours = 0…ExpenseAccount = true…
- 13. EDM & Entity Framework?The Entity Framework (EF) is an Object Relational Modeling tool leveraging the EDMFocus on your domain, not how to persist!EDM is used to describe your model.Allows different rate of change between database and code!EF uses a storage model and mapping to enable this.
- 15. EF Providers in Progress
- 16. LINQ to Entities – Lots of Topics
- 18. Pain Points in v3.5 SP1Pluralization/ SingularizationForeign KeysModel FirstLazy LoadingAdditional LINQ OperatorsL2S Features & PatternsSQL Gen Improvements
- 19. Fixing the Paint Points in EF1Advanced/ New Features
- 20. Model FirstCreate your conceptual model first (not from an existing database)Wizard will allow the creation of sql scripts to create database scripts.Also will create EDM filesCreates SQL Server, SQL Server Express, SQL Server Compact database scripts.
- 21. Lazy LoadingEnables retrieving all related data (without asking for it)Off by defaultSettable on the ContextOptionsGood for doing reporting!Not great for going across services Dim ctx As New AdventureWorksLT_DataEntities()ctx.ContextOptions.LazyLoadingEnabled = True
- 22. T4 TemplatesOverride default EF classes to create…POCO Entity GeneratorBetter for going over RESTful service layersSelf-Tracking Entity GeneratorBetter for server/ client local storage.Auto generates classes when models change!Or can be run manually.Easily modifiable for your own needsOnce you learn the T4 scripting language.
- 24. Summary
- 25. Conclusion
- 26. ResourcesADO.NET Team Bloghttp://blogs.msdn.com/adonet/default.aspxEF Design Blogblogs.msdn.com/efdesignVisual Studio Data Bloghttp://blogs.msdn.com/vsdata/dnrTV!http://shrinkster.com/1734http://shrinkster.com/1735
- 27. ResourcesDan Simmons Bloghttp://blogs.msdn.com/dsimmons/MSDN Code Galleryhttp://shrinkster.com/1733WCF Data Services Learning Guide:http://msdn.microsoft.com/en-us/data/bb931106.aspxWCF Data Services Team Bloghttp://blogs.msdn.com/astoriateam/default.aspx
- 28. Required Book!EF4 In Aug 2010
Editor's Notes
- #7: Goals:To show a new way of serving up dateGet you thinking to learn more when you leave this presentation
- #8: How do you or have you designed your applications??? Be truthful!!N-tier application architecture provides a model for developers to create a flexible and reusable application. By breaking up an application into tiers, developers only have to modify or add a specific layer, rather than have to rewrite the entire application over, if they decide to change technologies or scale up. In the term "N-tier," "N" implies any number -- like 2-tier, or 4-tier; basically, any number of distinct tiers used in your architecture. Application architectures are part of Layer 7 of the OSI model.
- #11: Talk about the separation between database developer and programmer.
- #12: Talk about the separation between database developer and programmer.
- #14: Applications can work in terms of a more application-centric conceptual model, including types with inheritance, complex members, and relationships.Applications are freed from hard-coded dependencies on a particular data engine or storage schema.Mappings between the conceptual model and the storage-specific schema can change without changing the application code.Developers can work with a consistent application object model that can be mapped to various storage schemas, possibly implemented in different database management systems.Multiple conceptual models can be mapped to a single storage schema.Language-integrated query (LINQ) support provides compile-time syntax validation for queries against a conceptual model.
- #17: POCO = Plane Old .NET Classes
- #18: Demo: AdventureWorks.DataDemo: AdvertureWorks.ExampleDemo: EntityDesignerDiagram.png
- #22: Demo: AdventureWorks.DataDemo: AdvertureWorks.ExampleDemo: EntityDesignerDiagram.png