Open bdelaney opened 8 years ago
This will only work up to EF6 because EF7 is a ground-up rewrite that doesn't have the same mapping layers that this library interrogates to generate its output.
https://github.com/aspnet/EntityFramework
EF Core is much more lightweight than previous versions and is built from the ground up
I don't know how much of what we have here could be re-used. I'm rather hoping they'll include the functionality directly and this library will be redundant.
I've marked this as wontfix because although it might be useful it's not immediately clear that this project would be the place for it. Maybe cannibalise the code and start a new project designed for EF7 (see licence for permission to do so).
Yes, understood. And I'll close this. For all we know, the EF team will include enum migrations. I took a look at the project here and notice there has been a lot of chatter around that. But then again, they have their hands pretty full. Thanks for taking the time to reply.
We shall see. I'm going to leave this issue open because if ms ever finish ef7 I'll need an answer too. Also a good signpost for other folks, I'm sure this will be a common question.
Worthy endeavor, agreed. Especially since I just manually coded 20 enums into lookup tables last night. :-)
Is there a possibility to use this with an EF7 web app if I include the EF6 libraries? I gave it a quick check in a seed class and it came up with a warning about needing the DbContext in EF 6.