When mapping database tables using ADO.NET Entity datamodel, why does Entity Framework utilize the ObjectContext instead of the DbContext?

asp.net asp.net-mvc-3 dbcontext entity-framework objectcontext


I am following the database approach first; I have created the tables in my SQL Server 2008 database, then I map those tables to Entity Framework classes using an ADO.NET Entity Data Model. But when I opened the designer.cs file I found the following code in the class definition which was created automatically:

public partial class PortalEntities : ObjectContext

so I have the following three question that get my confused:

  1. Why does my PortalEntities class derive from ObjectContext and not DbContext as I was expecting?

  2. Is there a major difference between ObjectContext & DbContext, or they are mainly the same and offer that same capabilities

  3. When I try to write the something similar to the following code:

    Student student = db.Students.Find(id);

I found that I cannot use .Find() method as I used to do using DbContext, so does this mean that ObjectContext & DbContext have different methods that I can use?


1/26/2012 3:53:36 PM

Accepted Answer

The DbContext is a wrapper around the ObjectContext which simplifies the interface for the things we do most.

If you have an DbContext you can still access the ObjectContexttrough ((IObjectContextAdapter)dbContext).ObjectContext;

If you want to use the DbContext instead of the ObjectContext when using database first, you can switch the template that's used for generating your code. You can do this by right-clicking in your EDMX and selecting 'Add Code Generation Item'. You can then select the DbContext template.

Here is an example of the whole process.

11/10/2012 7:44:34 AM

Popular Answer

Since VS2012 the default code generation changed from ObjectContext to DbContext.

Related Questions


Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow