I\'m using the DbContext
class within code that I am creating that is based on the Generic Repositories and Unit of Work design patterns. (I am following the gu
From ObjectContext VS DBContext.
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 of ObjectContext, but it is a simple alternative that builds on ObjectContext.
DbContext
is just a wrapper around ObjectContext
.
DbContext
is just a set of APIs that are easier to use than the APIs exposed by ObjectContext
.
Anyway, here you'll find a very simple Visual Studio template that uses the Repository Pattern and the Entity Framework.
We can cast a DBContext to type ObjectContext
public class MyContext: DbContext
{
public DbSet<Blog> Blogs { get; set; }
//other dbsets, ctor etc.
public ObjectContext ObjectContext()
{
return (this as IObjectContextAdapter).ObjectContext;
}
}