EF Core support for AutoMapper.Collection.EntityFramework

[embryologist]

Does AutoMapper Collection EntityFramework supports EF Core, installing it in my project gives me incompatibility issues,
if not what is the alternative ?

warning NU1701: Package 'AutoMapper.Collection.EntityFramework 3.1.3' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.1'. This package may not be fully compatible with your project.

[TylerCarlson1]

Entity Framework supports EF6 only. the code is only a couple of classes so I'm sure you can make a version for EF.Core extending from AutoMapper.Collections easily enough.

[ggirard07]

I'll add my +1 here as I am trying to migrate to ASP.Net Core :)

[Tasteful]

Now you can download and test the package for EFCore from MyGet (https://myget.org/feed/automapperdev/package/nuget/AutoMapper.Collection.EntityFrameworkCore)

[iotalambda]

@Tasteful Awesome! Works perfectly.

For googlers, note that the syntax is
cfg.SetGeneratePropertyMaps<GenerateEntityFrameworkCorePrimaryKeyPropertyMaps<MyContext>>();
instead of the traditional
cfg.SetGeneratePropertyMaps<GenerateEntityFrameworkPrimaryKeyPropertyMaps<MyContext>>();

Took a while to figure that out ^^

[replaysMike]

I'm getting an error when trying to use this configuration.

services.AddAutoMapper((cfg) => {
  cfg.AddCollectionMappers();
  cfg.SetGeneratePropertyMaps<GenerateEntityFrameworkCorePrimaryKeyPropertyMaps<ApplicationDbContext>>();
});

throws a "No parameterless constructor defined" exception. If I add one to my context, I then get:

No database provider has been configured for this DbContext. A provider can be configured by overriding the DbContext.OnConfiguring method or by using AddDbContext on the application service provider. If AddDbContext is used, then also ensure that your DbContext type accepts a DbContextOptions object in its constructor and passes it to the base constructor for DbContext.

However, my context does have a DbContextOptions constructor:

public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
            : base(options)
{
}

[replaysMike]

I was able to figure this out. It's because in my DbContext.OnConfiguring() has this line:

if (!string.IsNullOrEmpty(ConnectionString))
    optionsBuilder.UseSqlServer(ConnectionString);

I guess this extension tries to create a DbContext instance and it has no connection string passed so it fails. I had to add some logic to load up a default connection string to make this error go away, as the connection string is passed in for .net core EF setup using AddDbContext<>().

[Tasteful]

@replaysMike If you use DI you need in the first pre-release set the

mapper.ConstructServicesUsing(type => ActivatorUtilities.GetServiceOrCreateInstance(serviceProvider, type))

before calling the SetGeneratePropertyMaps method. The other way around is to pass in the IServiceProvider in an instance

x.SetGeneratePropertyMaps(new GenerateEntityFrameworkCorePrimaryKeyPropertyMaps<DB>(serviceProvider);

As you can see in AutoMapper/AutoMapper.Collection.EFCore#2 we are working to get up a solution to work better with the AutoMapper.Extensions.Microsoft.DependencyInjection package.

[Baune8D]

+1 for this ticket. This is the last component i need to migrate a project to .NET Core.

[Tasteful]

This has stalled because we need the new version of AutoMapper.Extensions.Microsoft.DependencyInjection out that is exposing the IServiceProvider during the configuration.

@jbogard any progress on this?

[Tasteful]

@jbogard You can close this one also, package is published on nuget.