The entity type type is not part of the model for the current context

Question

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 Added       dbSet Attach entity       lt -- The error occurs here      context SyncObjectState entity       The database    SQLEXPRESS  is created just fine  but the entities  tables  is just not created on startup    I am wondering if I need to explicit set the mapping of the entities  Is EF not able to this by its own    My Entity is   public class Estate   EntityBase       public int EstateId   get  set        public string Name   get  set         My context is as so   public partial class DimensionWebDbContext   DbContextBase    DbContextBase inherits DbContext       public DimensionWebDbContext             base  DimensionWebContext                 Database SetInitializer lt DimensionWebDbContext gt  new CreateDatabaseIfNotExists lt DimensionWebDbContext gt              Configuration ProxyCreationEnabled   false             public new IDbSet lt T gt  Set lt T gt    where T   class               return base Set lt T gt                Is there any specific reason why this error occurs  I have tried enable migrations and enable automatic migrations without any help either

User · Answer

This can also occur if you are using a persisted model cache which is out of date for one reason or another  If your context has been cached to an EDMX file on a file system  via DbConfiguration SetModelStore  then OnModelCreating will never be called as the cached version will be used  As a result if an entity is missing from your cached store then you will get the above error even though the connection string is correct  the table exists in the database and the entity is set up correctly in your DbContext

User · Answer

For me  the problem was that I used  List lt Some gt  someCollection       dbContext Remove someCollection    instead of   dbContext RemoveRange someCollection

User · Answer

if you are trying DB first then be sure that your table has primary key

User · Answer

My issue was resolved by updating the metadata part of the connection string  Apparently it was pointing at the wrong  csdl    ssdl    msl reference

User · Answer

For me the issue was that I had not included the Entity Class within my db set inside the context for entity framework   public DbSet lt ModelName gt  ModelName   get  set

User · Answer

For me the issue was that I used the connection string generated by ADO Net Model   edmx   Changing the connection string solved my issue

User · Answer

I was facing the same issue with EntityFrameworkCore trying to update a range of values   This approach did not work     dbSet AttachRange entity      context Entry entity  State   EntityState Modified     await  context SaveChangesAsync   ConfigureAwait false     After adding UpdateRange method and removing attach and entry everything work     dbSet UpdateRange entity     await  context SaveChangesAsync   ConfigureAwait false

User · Answer

I had this using  var context   new ATImporterContext DBConnection         if  GetID entity  Equals 0                 context Set lt T gt    Add entity             else               int val   GetID entity           var entry   GetEntryAsync context  GetID entity   ConfigureAwait false           context Entry entry  CurrentValues SetValues entity                   await context SaveChangesAsync   ConfigureAwait false      This was in an async method  but I ve forgot to put await before GetEntryAsync  and so I got this same error

User · Answer

One other thing to check with your connection string - the model name  I was using two entity models   DB first  In the config I copied the entity connection for one  renamed it  and changed the connection string part  What I didn t change was the model name  so while the entity model generated correctly  when the context was initiated EF was looking in the wrong model for the entities    Looks obvious written down  but there are four hours I won t get back

User · Answer

Put this in your custom DbContext class   protected override void OnModelCreating DbModelBuilder modelBuilder        modelBuilder Entity lt Estate gt    ToTable  Estate        If your tables are not created on startup  this is why  You need to tell the DbContext about them in the OnModelCreating method override    You can either do custom per-entity mappings here  or separate them out into separate EntityTypeConfiguration lt T gt  classes

User · Answer

map of the entity  even an empty one  added to the configuration will lead to having the entity type be part of the context  We had an entity with no relationship to other entities that was fixed with an empty map

User · Answer

The message was pretty clear but I didn t get it at first     I m working with two Entity Framework DB contexts sysContext and shardContext in the same method   The entity I had modified updated is from one context but then I tried to save it to the other context like this   invite uid   user uid   sysContext Entry invite  State   EntityState Modified   sysContext SaveChanges       Got the exception here   but the correct version should be this   invite uid   user uid   shardContext Entry invite  State   EntityState Modified   shardContext SaveChanges      After passing the entity to the correct context this error went away

User · Answer

Could be stupid  but if you only got this error on some Table  dont forget to clean your project and rebuild  could save a lot of time

User · Answer

Visual Studio 2019 seems to cause this for me  I fixed it by generating the edmx model again in 2017

User · Answer

Apparently  this error is very generic  it could have a number of reasons  In my case  it was the following  The connection string  in Web config  generated by the  edmx was invalid  After almost a day of trying everything  I changed the connection string from the EF string to an ADO NET string  This solved my issue   For example  the EF string looks something like this    lt connectionStrings gt      lt add name  BlogContext        connectionString  metadata res     BloggingModel csdl                                  res     BloggingModel ssdl                                  res     BloggingModel msl                                  provider System Data SqlClient                                 provider connection string                                   amp quot data source  localdb  v11 0                                  initial catalog Blogging                                 integrated security True                                  multipleactiveresultsets True  amp quot         providerName  System Data EntityClient    gt    lt  connectionStrings gt    And the ADO NET string looks like this    lt connectionStrings gt     lt add name  BlogContext            providerName  System Data SqlClient            connectionString  Server   SQLEXPRESS Database Blogging          Integrated Security True    gt    lt  connectionStrings gt    Source  http   msdn microsoft com nl-nl data jj556606 aspx

User · Answer

You may try removing the table from the model and adding it again  You can do this visually by opening the  edmx file from the Solution Explorer    Steps    Double click the  edmx file from the Solution Explorer Right click on the table head you want to remove and select  Delete from Model  Now again right click on the work area and select  Update Model from Database    Add the table again from the table list Clean and build the solution

User · Answer

Sounds obvious  but make sure that you are not explicitly ignoring the type   modelBuilder Ignore lt MyType gt

User · Answer

For me it was caused because I renamed the entity class When  I rolled it back it was Ok

User · Answer

I get same problem in Entity Framewrok  and I solved it by under steps    1-Open your Model edmx 2-change a table place  for do change in cs file  3-save it   I hope help you

User · Answer

Delete the  edmx file and add it again  Especially  if you have upgraded the Entity Framework

User · Answer

I ve seen this error when an existing table in the database doesn t appropriately map to a code first model  Specifically I had a char 1  in the database table and a char in C   Changing the model to a string resolved the problem

User · Answer

The problem may be in the connection string   Ensure your connection string is for SqlClient provider  with no metadata stuff related to EntityFramework

[c#] The entity type <type> is not part of the model for the current context

Examples related to c#

Examples related to entity-framework

Examples related to ef-code-first

Examples related to dbcontext