dbcontext

When should one call DbContext.dispose() with entity framework? Is this imaginary method bad? public static string GetName(string userId) { var context = new DomainDbContext(); var userName = context.UserNameItems.FirstOrDefault(x => x.UserId == userId); context.Dispose(); return userName; } Is this better? public static string GetName(string userId) { string userName; using(var context = new DomainDbContext()) { userName = context.UserNameItems.FirstOrDefault(x => x.UserId == userId); context.Dispose(); } return userName; } Is this even better, that is, should one NOT call context.Dispose()

This question already has an answer here: Entity Framework 4.0: How to see SQL statements for SaveChanges method 6 answers According this thread, we can log the generated SQL via EF , but what about DbContext.SaveChanges() ? Is there any easy way to do this job without any extra frameworks? In entity framework 6.0, the Database class has a property Action<string> Log . so setting up logging is as easy as: context.Database.Log = Console.WriteLine; For more advanced needs you can set up an interceptor . More info on the entity framework wiki See http://www.codeproject.com/Articles/499902

I am getting into the Entity Framework, but I am unsure if I am missing a critical point in the code-first approach. I am using a generic repository pattern based on the code from https://genericunitofworkandrepositories.codeplex.com/ and have created my entities. But when I try to access or modify the entity I run into the following: System.InvalidOperationException: The entity type Estate is not part of the model for the current context. It happens when I am trying to access it from my repository: public virtual void Insert(TEntity entity) { ((IObjectState)entity).ObjectState = ObjectState