Question

I keep getting error when I try to access a model from an edit or details action.

The model backing the ‘InjuriesContext’ context has changed since the
database was created. Consider using Code First Migrations to update
the database (http://go.microsoft.com/fwlink/?LinkId=238269).

First I tried adding a migration even though I was sure I hadn’t changed anything. Still recieved the same error after an update-database.

Then I removed all the migrations and the database and started a clean database with an inital migration and update. Same error. Nothing was changed.

Model is:

public class InjuriesContext : DbContext
    {
        public InjuriesContext()
            : base("DBCon")
        {
        }

        public DbSet<Patient> Patients { get; set; }

        public DbSet<Injury> Injuries { get; set; }
    }

    public class Injury
    {
        public int Id { get; set; }
        public string Type { get; set; }
        public int PatientId { get; set; }
    }

Here is controller —

public ActionResult Edit(int id = 0)
        {
            Injury injury = db.Injuries.Find(id);
            if (injury == null)
            {
                return HttpNotFound();
            }
            return View(injury);
        }

It errors on the injuries.find. I do not have any injuries entered so I expect it to return a 404 like my other controllers but it doesn’t like something about this. The only difference between this and my other models is the y to ies for plural. Does Entity Framework not handle this?

Answer 1

It turns out my issue was with multiple contexts. I thought you had to create a separate context for each model class. Apparently Entity Framework needs one context. I went through and created a class for my context and put all my DBsets in that class.

    public class ProjContexts : DbContext
    {
         public ProjContexts()
            : base("ProjDBCon")
        {
        }

        public DbSet<Patient> Patients { get; set; }
        public DbSet<PreHosp> PreHosps { get; set; }
        public DbSet<UserProfile> UserProfiles { get; set; }
        public DbSet<Injury> Injuries { get; set; }

    }
}

Then I removed all the migrations as per this post and enabled the migrations again did an add migration and update then I got the expected result.

Bottom Line— Don’t have multiple context classes in your project. Not sure if this is possible but after changing the above everything is working as expected. Not sure why it was working when I had two separate contexts and added the third? Maybe because they had foreign keys with one another?