I am following the same article as follows Managing Entity Framework ObjectContext lifespan. I generate the Entities from my EDMX file by using \"POCO Entity Generator\" tool and put all the Entities
I\'m trying to share a simple DbContext with 4 DbSets among multiple repositories, each of my repositories inherit from this base class
I\'m using an ObjectContext and storing it in HttpContext.Current.Items collection.I share the ObjectContext for a single request, but the framework also enables the ability to load a fresh, non-cache
I am working on a winform application with EF 4.0. Below code, crashes with issue \'The object cannot be detached because it is not attached to the ObjectStateManager.\' when it tries to detach the l
I was previously using a DataContext which had a GetTable(type) method to get tables generically.Example:
I have an ObjectContext with an update method.The method takes a generic object as a parameter.I need to attach this object to the ObjectContext and update the database with the changes the object had
I am new to Entity Framework 4.0, using it with C#, and currently experimenting with its features. What I noticed is that, like with most similar ORMs, it relies on an Context object to deal with the
Scenario: Trying to extract and rearange information from one database to an other. DB A has some data I want to get. I want to store it on DB B in a slightly different structure.
I\'m starting with the Entity Framework and the repository pattern. I\'m confused about the ObjectContext.
In ASP.NET MVC 2, using Entity Framework 4,I\'m getting this error \"An entity object cannot be referenced by multiple instances of IEntityChangeTracker\".