You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
The text was updated successfully, but these errors were encountered:
@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.
The text was updated successfully, but these errors were encountered: