Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automapper docs state they support .Net Standard 2.1 #4267

Closed
statler opened this issue Mar 29, 2023 · 0 comments
Closed

Automapper docs state they support .Net Standard 2.1 #4267

statler opened this issue Mar 29, 2023 · 0 comments

Comments

@statler
Copy link

statler commented Mar 29, 2023

@lbargaoanu I appreciate that you manage a big repo, but frankly, it would be more constructive not to close the issue then delete my discussion like it never happened, especially when it is not just valid, but I have also solved the issue and put a lot of effort into a solution. I created a fork and a pull request just to get "Automapper doesn't support EF6" which as far as I can see isn't supported by your documentation. Anyone else with the same problem will now not see that there is in fact a solution, or your response - which I am hoping you revisit.

I can find nowhere that states Automapper does not support EF6. The docs for v11+ literally say state AutoMapper now targets .Net Standard 2.1 and doesn’t work on .Net Framework. That is a reference to the framework, which is a completely different thing. EF6 is .Net Standard 2.1 compatible and I am running it in .Net 7, not framework. I could not find it anywhere that EF6 is not supported, so must conclude that this has not in fact been communicated, if it is actually correct.

That said, the changes I have proposed are literally all that is required to make it work, so it is very easy to continue supporting a very large part of the automapper universe that may still be stranded on v10 without this change. There are projects have to remain on EF6 due to its compatibility with specifie database types that EFCore doesnt target.

@AutoMapper AutoMapper locked and limited conversation to collaborators Mar 29, 2023
@lbargaoanu lbargaoanu converted this issue into discussion #4268 Mar 29, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant