Comments (10)
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.
from automapper.collection.
I'll add my +1 here as I am trying to migrate to ASP.Net Core :)
from automapper.collection.
@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 ^^
from automapper.collection.
@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.
from automapper.collection.
+1 for this ticket. This is the last component i need to migrate a project to .NET Core.
from automapper.collection.
Now you can download and test the package for EFCore from MyGet (https://myget.org/feed/automapperdev/package/nuget/AutoMapper.Collection.EntityFrameworkCore)
from automapper.collection.
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)
{
}
from automapper.collection.
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<>().
from automapper.collection.
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?
from automapper.collection.
@jbogard You can close this one also, package is published on nuget.
from automapper.collection.
Related Issues (20)
- Override GenerateEntityFrameworkPrimaryKeyPropertyMaps with EqualityComparison? HOT 2
- How to use Collections with Profile configuration? HOT 5
- When mapping Lists, if the DestinationType is added to a DataContext, automapper fails with an exception HOT 1
- How to use with a .Net 5 Web project and DI HOT 1
- EqualityComparison based on the index of item in collection
- Add support for AutoMapper 11.0.0 HOT 1
- Package version constraint violation with AutoMapper.Collection HOT 1
- Are nested lists supported?
- mapping foreign key
- EquivalentExpressionAddRemoveCollectionMapper should implement IObjectMapperInfo HOT 1
- Could not install on .NETFramework,Version=v4.8 HOT 2
- Support for AutoMapper v12 HOT 2
- Insert Master with details HOT 1
- DI cycles forever when calling AddCollectionMappers() twice HOT 3
- Collections with Automapper 12.0.1 doesn't work HOT 1
- Expression of type '<Type>' cannot be used for parameter of type '<OtherType>' of method 'Void Add(<OtherType>)' (Parameter 'arg0') HOT 3
- Attribute based EqualityComparison HOT 1
- Order of lists is not preserved during updates HOT 1
- Dependency Contraint HOT 1
- AutoMapper 13 support
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from automapper.collection.