article

Lesson 1 - Entity Framework

[WHAT]

  1. ] 

[WHY]

  1. ] 

[WHERE]

  1. ]

[WHEN]

  1. ] 2015-mm-dd

[EXAMPLE]

  1. [00:00] EF - outline course
    1. ] intro to ef
    2. ] beginning code first
    3. ] managing relationships -
    4. ] managing database - migrations
    5. ] manging transactions - dealing with the web environ ment
    6. ] integrating extras and looking forward - stored procedures, concurrency, future in ef7
  2. [00:00] preqequisites - course
    1. ] FOR developers -
    2. ] c# familiarity -
    3. ] intro to mvc - an intro level guide to the msft asp.net MVC framework, we are using MVC but its not the focus of this video, you can use EF in many different programming paradigms
  3. [00:00] module 1 - intro
    1. ] architecture
    2. ] intro to code first
    3. ] generating EF classes
  4. [00:00] architecture
    1. ] EF is an ORM, - ORM maps your database types to your code types
    2. ] used to avoid writing repititive data access code
    3. ] use to write code generates at all
    4. ] works with all SQL
  5. [00:00] EF 
    1. ] EF 6.1 any project that is asp.net 4+
    2. ] all msft SQL db's
    3. ] programming paradigms - web forms, web api, MVC, (+web pages), wpf, wcf ,
    4. ] newer versions to include Azure Table storage, reddis, linux, etc
    5. ] supported ado.net providers - most major RDBM's including mysql, oracle, IBM, sybase, postgres
  6. [10:15] EF - features
    1. ] Full ORM to map objects to code - takes stuff in db and matches to your code and vice versa
    2. ] Asynch queries -
    3. ] Connection Resiliency - retry on connection failures
    4. ] StoredProcedure mapping
    5. ] Reverse Engineering Existing Database - create code from existing database
    6. ] using code to create database ( code first)
    7. ] concurrency detection -
    8. ] enum and spatial data support -
    9. ] many more features -
  7. [12:00] EF - how it works ( high level overview)
    1. ] illustration - basic ] link to entities, ] convert to query, execute ] map results to entitity  
    2. ] illustration - advanced( EF system components) - ] more detailed workflow description of EF
    3. ] this course will focus on the basic - you write some LINQ, you get results back
  8. [13:00] EF - installation
    1. ] requires VS 2010 or >
    2. ] use Nuget "Install-package EntityFramework"
    3. ] comes with /MVC, /WEB FORMS, /WEB-API if Identity is used
    4. *] there is a gui for it, can use console ( NuGet ? EF )
  9. [14:00] NuGet Primer
    1. ] Install-Package {PackageName} - installs latest non beta version
    2. ] Install-Package EntityFramework - pre - installs lateste pre release version
    3. ] Uninstall-Package {PackageName}
    4. ] Update-Package EntityFramework - reinstall (all projects)
    5. ] Update-Pakage EntityFramework -ProjectName MyProject
    6. *] 31K packages available
  10. [15:30] DEMO - install EF into new Console application using NugetPackage manager
    1. ] new console project
    2. ] use PM console window cmd to install EF into project
    3. ] Install-Package EntityFramework
    4. ] review package.config - to review packages installed, (EF 6.1.2 is the only currently installed package)
    5. +] REFERENCE - nuget website package name - shows addtional info details, package version history
  11. [18:00] DEMO - install EF into new Web application
    1. ] new project - points out "Web application" template and OPTION for Identity settings - change authentication
    2. +]  REFERENCE - MVA course on Identity by Adam and Jeremy
    3. ] installs web application template with No authentication
    4. ] points out EF is not installed with this template
    5. ] then uses PM console to install EF into project as per previous DEMO
  12. [20:15] Intro to (EF) code first
    1. ] code first - a misnomer - write code first, then the code will create the database
    2. ] usually in enterprise development, you have an existing database and you work with that OR in some cases, design the db,  but its still that's the first step
    3. ] takes your PLAIN OLD CLR OBJECTS (POCO) and maps them to database tables
    4. ] only requires 2 things ] a context class ] your code class
    5. ] context class = everything you are going to do with your database, goes through your context class
  13. [22:15] DEMO basic code first (console app)
    1. ] PROS- EF - more fluid, efficient way of developing, stay in the code,
    2. ] example - album class, access data from database via console application
    3. ] get count of records in db - var count = context.Albums.Count()
    4. ] adds album to db - context.Albums.Add( new Album(){price:9.99, title="Wish"})
    5. ] create a query against db using linq
    6. ] var albums = context.Albums .Where( o=> o.Title.Contains("Wish")).ToList();
    7. ] did all of this 'db work' without really doing anything db related,
    8. ] intellitrace shows all queries you are making from your code (ultimate edition of VS )
  14. [34:15] DEMO basic code first and scaffolding (web app )
    1. ?] ? re: data context - keep reusing the same one or create new ones - uses ADO.net behind the scenes, manages connection pooling , there wont be any performance hit by creating a new context each time, after its used it goes back into a pool, if another request comes in for same database, it uses the existing connection
    2. x] creates new app using template with Identity ( this includes the album framework)
    3. x] adds the "album" class with a Music dbContext class 
    4. x] add controller - new scaffolded item (mvc5 controller with views using EF) - set model, set dbcontext
    5. *] you have the option to ADD a dbcontext if none exists, in this dialog (use the + icon beside ) -
    6. *] this auto generates the Controller class, contains methods for add,delete,list,edit along with view for each also
    7. x] access the new controllers by yourapp.com/Albums
    8. x] creates new album - adds and displays the album
  15. [39:30] how does EF connect to your db
    1. ] dbs can be in many different places ( App_Data, intranet, cloud )
    2. ] do you have an existing named connection string in your web.config?
    3. ] if EF finds a connection string named "" in your web.config it will connect to that db (connection string named in dbContext class )
    4. ] looks in web config for conn string named the same as you class (use ContextClass name )
    5. ] IF no connection string found looks for ] sql express on your system, then ] local db \\11 , ] local db 12 ( mssqllocaldb) and then creates db
    6. ] TIP you should always SPECIFY a connection string name if you know what database you are going to use
    7. ] EXAMPLE = public MusicContext():base("MusicStoreConnection")
    8. ] WHERE MusicStoreConnection is the name of a connection string that exists in your web.config file
  16. [43:00] TIP checking whats installed on your system
    1. ] from command prompt or powershell
    2. ] sqllocaldb i - mssql db installed
    3. ] sqllocaldb v - sql server versions installed
    4. ] be aware of what your connecting to
  17. [44:00] Viewing - db Queries
    1. ] 3 ways to look at the queries you are generating against the db, for debugging, ...
    2. ] vs ultimate edition has built in "intellitracer"
    3. ] basic way - Context.database.log = s => Console.WriteLine(s)
    4. ] free tool - glimpse -
    5. ] Install-Package glimpse.mvc5, Install-Package glimpse.ef6
    6. ] Intercepter - goes in .config file, outputs to a log file
  18. [46:00] DEMO - viewing queries
    1. ] using Debug and Console.Writeline
    2. ] using glimpse - installs the 2 aforementioned packages
    3. ] a great development tool, like browsers f12 dev tools for your mvc app , includes realtime debugging info for sql statements as well
  19. [51:00] Generating EF classes
    1. ] hand coding -  write classes as you would normally write classes in code only
    2. ] using a visual designer - *] the VD will be DISCONTINUED in ef7
    3. >] Add - ADO.net entity data model -  
    4. ] database first entity designer -
  20. [52:00] DEMO - database first
    1. ] USE ADO.net entity data model - to point to an existing db and reverse engineer it to create the classes that you need in your project
    2. ] ADD new item to project, new data item, ado.net entity data model, enter name of what will the dbContext class should be
    3. ] dialog - SELECT -what should the model contain ( code first from database)
    4. ] select or enter - connection | database
    5. ] will visit this in more detail in another lesson

[HOW-TO]

  1. ]

[REFERENCE]

  1. ]

 

 

status - 15% completed course (+10 points) #102213 in MVA ranking, # 1441 in your country's ranking

quiz result = 4/5

 

quiz


What kind of framework is the Entity Framework?
Which two solutions can be used to view queries when using the Entity Framework? (Choose two.)
x] Which three of the following statements correctly describes the benefit of using an ORM? (Choose three.


Automates database queries
Avoids writing repetitive code
Creates business logic in the code
Handles database transactions
Maps multiple database tables to classes
 

Details Photos Edit more

Details

ID: 4591

NAME: Lesson-1-intro-to-entity-framework

DESCRIPTION: [55:00]VIDEO-SUMMARY-

AUTHOR: article.author/s

EDITOR: article.editor/s

PUBLISHER: article.publisher/s

STATUS: Write

PRIORITY: 0

OWNER ID: 75

Content Photos Edit more

photos

page_photo

actions

Email Email-Owner SMS and