http://www.entityframeworktutorial.net/Types-of-Entities.aspx

We created EDM for existing database in the previous section.

As you have learned in the previous section that EDM contains entities for each table in the database.

There are two types of Entities in Entity Framework 5.0/6.0: POCO entity and dynamic proxy entity.

The Entity Framework enables you to use custom data classes together with your data model without making any modifications to the data classes themselves. This means that you can use "plain-old" CLR objects(POCO), such as existing domain objects, with your data model.

POCO Entity (Plain Old CLR Object):

POCO class is the class that doesn't depend on any framework specific base class. It is like any other normal .net class which is why it is called "Plain Old CLR Objects".

These POCO entities (also known as persistence-ignorant objects) support most of the same query, insert, update, and delete behaviors as entity types that are generated by the Entity Data Model.

The following is an example of Student POCO entity.

using System;

    using System.Collections.Generic;

    public partial class Student

    {

        [System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Usage", "CA2214:DoNotCallOverridableMethodsInConstructors")]

        public Student()

        {

            this.Courses = new HashSet<Course>();

        }

        public int StudentID { get; set; }

        public string StudentName { get; set; }

        public Nullable<int> StandardId { get; set; }

        public byte[] RowVersion { get; set; }

        public virtual Standard Standard { get; set; }

        public virtual StudentAddress StudentAddress { get; set; }

        [System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Usage", "CA2227:CollectionPropertiesShouldBeReadOnly")]

        public virtual ICollection<Course> Courses { get; set; }

    }

Dynamic Proxy (POCO Proxy):

Dynamic Proxy is a runtime proxy class of POCO entity. It is like a wrapper class of POCO entity.

Dynamic proxy entities allow lazy loading andautomatic change tracking.

POCO entity should meet the following requirements to become a POCO proxy:

1. A POCO class must be declared with public access.
2. A POCO class must not be sealed (NotInheritable in Visual Basic)
3. A POCO class must not be abstract (MustInherit in Visual Basic).
4. Each navigation property must be declared as public, virtual
5. Each collection property must be ICollection<T>
6. ProxyCreationEnabled option must NOT be false (default is true) in context class

The following Student POCO entity meets all of the above requirement to become dynamic proxy entity at runtime.

using System;

    using System.Collections.Generic;

    public partial class Student

    {

        [System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Usage", "CA2214:DoNotCallOverridableMethodsInConstructors")]

        public Student()

        {

            this.Courses = new HashSet<Course>();

        }

        public int StudentID { get; set; }

        public string StudentName { get; set; }

        public Nullable<int> StandardId { get; set; }

        public byte[] RowVersion { get; set; }

        public virtual Standard Standard { get; set; }

        public virtual StudentAddress StudentAddress { get; set; }

        [System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Usage", "CA2227:CollectionPropertiesShouldBeReadOnly")]

        public virtual ICollection<Course> Courses { get; set; }

    }

Note: By default dynamic proxy is enabled for every entity.

However, you can disable dynamic proxy by setting the ProxyCreationEnabled option to false in context class.

context.Configuration.ProxyCreationEnabled = false;

EDM generates POCO entities which satisfy the above requirements for a dynamic proxy by default.

At runtime, type of Student will be System.Data.Entity.DynamicProxies.Student as below:

Getting the actual entity type from a dynamic proxy:

You can use ObjectContext.GetObjectType() to find the actual type of dynamic proxy as shown below:

Entity can have two types of properties, Scalar and Navigation properties.

Scalar properties:

Scalar properties are properties whose actual values are contained in the entity.

For example, Student entity has scalar properties like StudentId and StudentName.

These correspond with the Student table columns.

Navigation properties:

Navigation properties are pointers to other related entities.

The Student has Standard property as a navigation property that will enable the application to navigate from a Student to related Standard entity.