Storing DbSet in constructor instead of calling DbContext.Set for every use

Error passing existing connections to DbContext constructor when using Database-First

Connection strings used by the designer are not regular connection strings. Rather they are ...EntityConnection... strings. The difference is that entity connection strings contain additional information about where to find metadata describing the model which is in form of the edmx at design time - read more ...here.... Code First uses just regular...

DbSet.Add & DbSet.Remove Versus using EntityState.Added & EntityState.Deleted

From Lerman & Miller's DbContext book (p. 80):...Calling ...DbSet.Add... and setting the ...State... to ...Added... both achieve exactly the same thing....Which is:...If the entity is not tracked by the context, it will start being tracked by the context in the ...Added... state. Both ...DbSet.Add... and setting the ...State... to ...Added... are...

What if I call DbContext.Dispose without calling DbContext.SaveChanges?

I am looking for a way to roll back entity changes. I came across ...this answer... which shows how to set entity state, but I am wondering what happens if I simply dispose of my ...dbContext... instance without calling ...dbContext.SaveChanges()... or manipulating the entity states....The code I wrote to do so definitely works, but am I leaving a...

Why DbContext autometically disposed after every api call in EF Core?

Changing the lifetime of your ...IUserRepository... will not affect the lifetime of the ...DbContext.... There's an ...overload... of ...AddDbContext... that allows you to specify the lifetime of the ...DbContext.... e.g....services.AddDbContext<MyDbContext>(options => { options.UseSqlServer(Configuration.GetConnectionString("DbCon")); }, Servi...

IBM.EntityFrameworkCore - DbContext.OnConfiguring and DbContext.OnModelCreating aren't called

I've found the reason. It turned out that it's about ...Microsoft.EntityFrameworkCore... version. Currently available version of ...IBM.EntityFrameworkCore... is ...1.1.1.101... (.NET Standard 1.6), and it uses ...Microsoft.EntityFrameworkCore... version ...1.1.1... or ...1.1.2.... It ...cannot... be used with ...Microsoft.EntityFrameworkCore... ve...

How to call stored procedure in EF Core v2.1 and set result to custom model?

In EF 6, I use this code that calls a stored procedure and returns result as a custom model....var pShippingMethodId = _dataProvider.GetParameter(); pX.ParameterName = "X"; pX.Value = x; pX.DbType = DbType.Int32; var pStoreId = _dataProvider.GetParameter(); pY.ParameterName = "Y"; pY.Value = y; pY.DbType = DbType.Int32; var pLanguageId = _dataPr...

Rollback additions / removals to DBSets of the DbContext using a transaction in Entity Framework

Option #1 from ...https://code.msdn.microsoft.com/How-to-undo-the-changes-in-00aed3c4... is typically enough for most implementations where you want to roll-back changes in the DbContext without dropping and re-instantiating a Context. Generally the request would have failed and the call would have ended so the DbContext scope should end until a re...

Azure Function Uses Wrong DbContext Constructor

You may refer to: ...Service registration methods...If there are multiple constructors, you can specify one as following:...Add{LIFETIME}<{SERVICE}>(sp => new {IMPLEMENTATION}) ...For example:...// Constructor1 builder.Services.AddScoped<IMyDep>(sp => new MyDep()); // Constructor2 builder.Services.AddScoped<IMyDep>(sp => new MyDep("A string!")); ...

How to call stored procedure in Entity Framework Core with input and output parameters using mysql

I am using ASP.net Core 2.2 with Entity Framework core 2.2.6 and Pomelo.EntityFrameworkCore.MySql 2.2.0 for connectivity with MySQL, I have a stored procedure which takes 3 input parameters and 1 output parameter. I am able to call it in MySQL workbench like...CALL GetTechniciansByTrade('Automobile', 1, 10, @total); select @total; ...Now I want to ...

Ambiguous call when using LINQ extension method on DbSet<T>

This problem is caused by a combination of using the ...System.Linq.Async... package and the ...DbSet<TEntity>... class, which implements both ...IQueryable<TEntity>... and ...IAsyncEnumerable<TEntity>.......In this situation, importing the namespaces ...System.Linq... and ...Microsoft.EntityFrameworkCore... leads to the definition of the conflicti...