Hi René,

I know I'm not solving your actual problem but could you use a separate SQL database for EF? That was the approach I took and managed to get things wired up ok!

Just a thought :)

Lotte

There are people who believe that using a separate database for non umbraco data is the safer / right approach to take anyway! At least then you know that Umbraco migrations and EF migrations would never have any conflict. Good luck :)

I just came across the same issue. I resolved by adding the following references in the project file, Item group:

<PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="7.0.0" />
<PackageReference Include="Microsoft.Extensions.Options" Version="7.0.0" />

The build status told me which packages to reference.

I ran into this issue in 13.5.2 recently and none of the above worked for me. The problem was that I was following the Umbraco documentation for connecting for custom data which applies to data within the same database as the main Umbraco instance.

There was a chat over in Discord that helped me out, basically instead of builder.Services.AddUmbracoDbContext you should use builder.Services.AddDbContext and then instead of using the IEFCoreScopeProvider use a TransactionScope, like so:

builder.Services.AddDbContext<MyDbContext>((serviceProvider, options) =>
{
    options.UseSqlServer(builder.Config.GetConnectionString("customDbDSN"));
});

Elsewhere in your code....

public class CustomDataRepository(MyDbContext myDbContext)
{
    public async Task<IEnumerable<SomeClass>> GetAll()
    {
        using (var scope = new TransactionScope())
        {
            var data = myDbContext.SomeClasses.ToList();
            scope.Complete();
            return data;
        }
    }
}

Here's the Discord chat for more reference.

is working on a reply...