ObjectContext VS DBContext

Jignesh Trivedi

3y366.9k12100Article

DbContextObjectContextObjectStateManagerMetadata in EDM

12 Comments

Join the conversation! Your thoughts help the community grow.

Pasang Tamang3y ago
Nice article with good explanation
Uday Dodiya4y ago
Excellent work
Pawan Verma7y ago
Dbcontext is lightweight version of Object context. How can you prove it?
Dipak Shinde9y ago
Which one better to use ObjectContext Or DbCOntext
- Dipak Shinde9y ago
  I have a doubt of regarding Object context or Db Context . Hope you will explain me. 1. if i used object context , then it will provide in build insert,update,delete operation. that one is good but bulk insert,update,delete is not Providing. so can continue to use ? 2 . can Db Context will Provide bulk insert,update,delete operation.
- Jignesh Trivedi9y ago
  Dbcontext is lightweight version of Object context. If you required functionality support by both object context and dbcontext, so better to use dbcontext. hope this is answer of your question.
Bhavik Patel10y ago
good one
Mahesh Alle10y ago
Excellent work.... Thanks....
Pramod Lawate11y ago
good explanation ..
Sudheer Kumar12y ago
Good article
Sai Sherlekar12y ago
good
Hendrawan Haryanto13y ago
wow great explanationss..

Introduction

ObjectContext and DbContext have the capability to query and work with data as objects. Additionally, Dbcontext can be represented as a combination of the Unit of Work and Repository patterns. Conceptually DbContext is the same as ObjectContext.

ObjectContext

ObjectContext is a class that manages all the database operations, like database connection, and manages various entities of the Entity Model. We can say that ObjectContext is the primary class for accessing or working together with entities that are defined in the conceptual model.

ObjectContext is responsible for

Database connection
It provides built-in Add, Update and Delete functions
Object Set of every entity
Provide State of pending changes
It holds the changes done in entities

ObjectContext also encapsulates a few things

Connection to the Data Store or Database
Metadata in the Entity Data Model (EDM)
ObjectStateManager to track changes to the objects

DbContext

DbContext is conceptually similar to ObjectContext. DbContext is nothing but an ObjectContext wrapper, we can say it is a lightweight alternative to the ObjectContext. DbContext can be used for DataBase first, code first and model first development. DbContext mainly contains a set of APIs that are very easy to use. The API is exposed by ObjectContext. These APIs also allow us to use a Code First approach that ObjectContext does not allow.

ObjectContext VS DbContext

ObjectContext	DbContext
ObjectContext class is part of the core Entity Framework API, which allows us to perform queries, change and track updates of the Database by using strongly typed entity classes.	The DbContext class can be described as a wrapper of ObjectContext. It exposes the most commonly used features of ObjectContext.
ObjectContext supports Compiled Queries.	DbContext does not support Compiled Queries.
ObjectContext supports the self-tracking of Entities	DbContext does not support the self-tracking of Entities.
ObjectContext is only useful in Model First and Database First approaches	DbContext is useful in the Model First, Database First approach as well as Code First approach.
ObjectContext can be used by Entity Framework 4.0 and below.	DBContext can be used by Entity Framework 4.1 and above.
The ObjectContext class is not thread-safe.	Any public static (C#) or Shared (Visual Basic) members of DbContext are thread-safe. Any instance members are not guaranteed to be thread-safe.

There are also many methods in common in both ObjectContext and DbContext. For example, ObjectContext has a direct method to execute a query against a database whereas the DbContext.Database class contains the SQLQuery method to obtain the same result.

Example

// using ObjectContext (EF4.0) using (
  Entities context = new Entities()
) {         IEnumerable < EmployeeDetails > empDetails   =  context.ExecuteStoreQuery < EmployeeDetails >     ("exec GetEmployeeData").ToList();
} // using DBContext (
  EF 4.1 
  and above
) using (
  Entities context = new Entities()
) {         IEnumerable < EmployeeDetails > empDetails   =  context.Database.SqlQuery                                                                       < EmployeeDetails >("exec GetEmployeeData ", null).ToList();
}

DbContext also has some sets of methods that are not available with ObjectContext, like Dbset. Find, DbSet.Local etcetera.

Some of the ObjectContext methods are also renamed. For example, ObjectContext has methods like AddObject, DeleteObject, And Attach on ObjectSet<T>, in DbContext, they are named Add, Remove and Attach on DbSet<TEntity>.

Conclusion

Dbcontext can be defined as a lightweight version of the ObjectContext or we can say Dbcontext is a wrapper of ObjectContext and exposes only the common features that are really required in programming.

We can also get a reference to the ObjectContext from then DbContext to use those features that are only supported in ObjectContext.

The following code could help to get an ObjectContext Object from an existing DbContext Object.

public class EntityDBContext: DbContext, 
IObjectContextAdapter {    
ObjectContext IObjectContextAdapter.ObjectContext    
{         get         {               var objectContext = (this as IObjectContextAdapter)               if(objectContext != null)                 
return (this as IObjectContextAdapter).ObjectContext;
              else                 return null;
        }    } }

Finally, DbContext is not a replacement for ObjectContext, but it is a simple alternative that builds on ObjectContext.

Hope this will help to understand the differences between ObjectContext and DbContext.