-
Notifications
You must be signed in to change notification settings - Fork 15
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
EF Classic? #66
Comments
Hey. This project depends on the |
That's a likely no. I think the |
Yeah, that's unfortunate. It was already a challenge to make this work with the fully available tooling in EF6. |
It's honestly such a pain. I'm on a deadline to get an ASP.NET Core EF6 app moved from Azure to Linux VMs which would ideally include moving to .NET Core fully, and finally we have EF6 versions that run on Core but no migration tooling which is super important :( |
We also had to make our peace with sticking with full .NET for one of our large projects because we need EF6. Nothing can be done here but wait for EF6 to become .NET standard. |
Sadly, I cannot wait unless I am willing to risk running this web app on Mono, and I'm not sure that's a safe bet... |
Hey there, do you think there is any reasonable way to make this work with ZProject.EntityFramework.Classic? It's an EF6 fork that runs on .NET Core/netstandard, but has no migration tooling
The text was updated successfully, but these errors were encountered: