DEV Community

EF Core multiple Database providers

Mohsen Esmailpour on May 11, 2021

Most of the time you don't need to have multiple database providers, for example, you start with the SQL Server provider and there is no need to sw...

Read full post

Can Ürek • Apr 9 '23

I couldn't use this approach with the IdentityDbContext. TContextService and TContextImplementation logic don't work as expected. And I got an error like this;

"An error occurred while accessing the Microsoft.Extensions.Hosting services. Continuing without the application service provider. Error: Some services are not able to be constructed (Error while validating the service descriptor..."

Do you have any idea to fix this situation?

Mohsen Esmailpour • Apr 10 '23 • Edited

I upgraded the sample project in GitHub to .NET 7.0 and it's working fine. Please follow the sample project or share your codes by a git repo.

Can Ürek • Apr 10 '23

Thanks for the reply. I handled it somehow. I'll also look at your repo.

nomada2 • May 12 '21

can you add nosql database like azure cosmos documentdb?

Mohsen Esmailpour • May 12 '21

Sure, it's just like PostgresSQL but it does not need to generate migration at all, and by calling context.Database.EnsureCreated() database will be created. Check out the sample project on github.

nomada2 • May 12 '21

thanks, i'll check

magals • Dec 4 '22

Is there a way to get rid of options.UseSqlServer(Configuration.GetConnectionString("MsSqlConnection")); to MsSqlDbContext and pass the connection string when services.AddDbContext(); ?

I ask because if the work with DbContext is transferred to a separate project as a library, then it will not be correct for this library to have a strictly fixed entry to the path to the Database. (Configuration.GetConnectionString("MsSqlConnection"))

Mohsen Esmailpour • Jan 6 '23

@magals you can inject a model that has a connection string property instead of IConfiguration to DbContext and get ride of hardcoded key name.

public class SqlServerDbContext(ConnectionStringModel model)
{
    protected override void OnConfiguring(DbContextOptionsBuilder options)
    {
       options.UseSqlServer(_model.ConnectionString);
    }
}