Skip to content
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

Open
kanadaj opened this issue May 24, 2019 · 6 comments
Open

EF Classic? #66

kanadaj opened this issue May 24, 2019 · 6 comments

Comments

@kanadaj
Copy link

kanadaj commented May 24, 2019

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

@mrahhal
Copy link
Owner

mrahhal commented May 24, 2019

Hey. This project depends on the EntityFramework package's migration tooling for the real work. The question here is whether ZProject.EntityFramework.Classic contains the equivalent migration types I'm using. I haven't used it so I don't really know. All in all, it's possible as I don't really depend on full .NET apart from using EF6 itself, but it'll possibly need lots of work.

@kanadaj
Copy link
Author

kanadaj commented May 24, 2019

That's a likely no. I think the EntityFramework package's tooling might only work with the legacy project format which is already a problem :(

@mrahhal
Copy link
Owner

mrahhal commented May 24, 2019

Yeah, that's unfortunate. It was already a challenge to make this work with the fully available tooling in EF6.

@kanadaj
Copy link
Author

kanadaj commented May 24, 2019

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 :(

@mrahhal
Copy link
Owner

mrahhal commented May 24, 2019

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.

@kanadaj
Copy link
Author

kanadaj commented May 24, 2019

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants