Use both AddDbContextFactory() and AddDbContext() extension methods in the same project

by

It is, it’s all about understanding the lifetimes of the various elements in play and getting those set correctly.

By default the DbContextFactory created by the AddDbContextFactory() extension method has a Singleton lifespan. If you use the AddDbContext() extension method with it’s default settings it will create a DbContextOptions with a Scoped lifespan (see the source-code here), and as a Singleton can’t use something with a shorter Scoped lifespan, an error is thrown.

To get round this, we need to change the lifespan of the DbContextOptions to also be ‘Singleton’. This can be done using by explicitly setting the scope of the DbContextOptions parameter of AddDbContext()

services.AddDbContext<FusionContext>(options =>
    options.UseSqlServer(YourSqlConnection),
    optionsLifetime: ServiceLifetime.Singleton);

There’s a really good discussion of this on the EF core GitHub repository starting here. It’s also well worth having a look at the source-code for DbContextFactory here.

Alternatively, you can also change the lifetime of the DbContextFactory by setting the ServiceLifetime parameter in the constructor:

services.AddDbContextFactory<FusionContext>(options => 
    options.UseSqlServer(YourSqlConnection), 
    ServiceLifetime.Scoped);

The options should be configured exactly as you would for a normal DbContext as those are the options that will be set on the DbContext the factory creates.

More Related Contents:

  1. One DbContext per web request… why?
  2. Dependency injection in unit of work pattern using repositories
  3. Register AspNetCore 2.1 Identity system with DbContext interface
  4. Entity Framework change connection at runtime
  5. Dependency Injection Unity – Conditional Resolving
  6. How to update record using Entity Framework 6?
  7. Entity Framework Refresh context? [closed]
  8. Validation failed for one or more entities while saving changes to SQL Server Database using Entity Framework
  9. DbEntityValidationException – How can I easily tell what caused the error?
  10. Does Entity Framework Code First support stored procedures?
  11. Entity Framework 6 GUID as primary key: Cannot insert the value NULL into column ‘Id’, table ‘FileStore’; column does not allow nulls
  12. Save and retrieve image (binary) from SQL Server using Entity Framework 6
  13. Insert data using Entity Framework model
  14. Setting unique Constraint with fluent API?
  15. Lazy Loading vs Eager Loading
  16. Does Entity Framework 4 Code First have support for identity generators like NHibernate?
  17. Entity Framework Filter “Expression”
  18. How to get property change notifications with EF 4.x DbContext generator
  19. Use dependency injection in static class
  20. LINQ to Entities does not recognize the method ‘System.Web.Mvc.FileResult’
  21. Problems using Entity Framework 6 and SQLite
  22. The remote server returned an unexpected response: (413) Request Entity Too Large.
  23. Setting the default value of a DateTime Property to DateTime.Now inside the System.ComponentModel Default Value Attrbute
  24. Log Queries executed by Entity Framework DbContext
  25. An error occurred while saving entities that do not expose foreign key properties for their relationships
  26. Entity Framework Code First Date field creation
  27. “Context cannot be used while the model is being created” exception with ASP.NET Identity
  28. How to force LINQ Sum() to return 0 while source collection is empty
  29. How to use String property as primary key in Entity Framework
  30. Implementing recursive property loading in EF Core

Leave a Comment