The Users property is added for convenience, so you don’t need to remember what all of your tables are and what the corresponding class is for it, you can use Intellisense to see all of the tables the context was designed to interact with. The end result is functionally equivalent to using Set<T>.
It looks like there are several classes that have been inherited from DbContext class (may have come from some NuGet package). So add migration with Add-Migration MyMigration -context DataContextName
This happens because of NSubstitute syntax specific. For example in: ((IQueryable<Blog>) mockSet).Provider.Returns(data.Provider); NSubstitute calls the Provider’s getter, then it specifies the return value. This getter call isn’t intercepted by the substitute and you get an exception. It happens because of explicit implementation of IQueryable.Provider property in DbQuery class. You can explicitly create substitutes for multiple … Read more
It just attaches the entity to the dataContext. Otherwise you will have to search for the entity using the primary key and then edit the value and save it. If you have an entity that you know already exists in the database but to which changes may have been made then you can tell the … Read more
With Entity Framework Core (tested with Version 2.1) you can get the current context using // DbSet<MyModel> myDbSet var context = myDbSet.GetService<ICurrentDbContext>().Context; How to get a DbContext from a DbSet in EntityFramework Core 2.0
The point is that Find() starts by searching in the local cache of the context and then, if no match, sends a query to the DB. Call to Where() always sends a query to the DB. With EF 4, I used to think that SQL generated by Find() was too complex and, in some cases, … Read more
EFCore 3 – They FINALLY fixed this! You can now implement OnModelCreatingPartial in a partial class like this. Note the partial keyword on both the class and method: public partial class RRStoreContext : DbContext { partial void OnModelCreatingPartial(ModelBuilder builder) { builder.Entity<RepeatOrderSummaryView>().HasNoKey(); } } If you look at the generated context file – right at the … Read more
I believe EF should update your entity object with the identity: var entity = new Entity_Table { item1 = val1, item2 = val2 }; dbcontext.Entity_Tables.Add(entity); dbcontext.SaveChanges(); int newPK = entity.ID;
Try to add this to your DbContext tests: dbContext.Configuration.AutoDetectChangesEnabled = false; // Now do all your changes dbContext.ChangeTracker.DetectChanges(); dbContext.SaveChanges(); and try to run your tests again. There was some architectural change in DbContext API which checks changes in entities every time you Add, Attach or Delete anything from the context. In ObjectContext API this detection … Read more
I figured it out. This mostly came about because I accidentally deleted the database that Identity was using and I needed to figure out how to get it back. Apparently there’s nothing wrong with my connection string the way it is. I just needed to go into the package manager and type these commands in … Read more