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

Any interest in an Entity Framework to EF Core porting reference document? #22941

Closed
jonlouie opened this issue Oct 10, 2020 · 2 comments
Closed

Comments

@jonlouie
Copy link
Contributor

Would the EF Core team be interested in adding a reference guide for porting from Entity Framework to EF Core?

A couple of weeks ago I heard there might be interest in collaborating on such a document so I wanted to raise the question in a public forum. It would include things like:

  • Syntactical differences
  • Behavioral changes
  • Feature disparity
  • Etc.

This list could be expanded to include other topics such as Porting Guidance (when to upgrade to EF6 vs migrating to EF Core) or anything else that the community might find useful. The main goal would be to bring all of this information to a central, community-built knowledge base.

Here is what I have so far: https://github.com/jonlouie/docs-sandbox/blob/master/README.md

If there any interest in adding this type of content, I'm all ears for any suggestions and would be happy to collaborate.

@AndriySvyryd
Copy link
Member

Yes, this is something that we are interested in as there is still a significant number of users who haven't ported to EF Core. The content should loosely follow the existing structure on feature comparison and porting tips.

The main issue tracking this is dotnet/EntityFramework.Docs#1180, so I'll close this one as duplicate. That issue contains a link to a video that could be useful.
Also consider these related issues: dotnet/EntityFramework.Docs#684, dotnet/EntityFramework.Docs#1971, dotnet/EntityFramework.Docs#1989

@jonlouie
Copy link
Contributor Author

@AndriySvyryd Thank you for the information and feedback. I'll take a look at the materials you've outlined to see where I can contribute.

@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants