Help Us Plan EF Core 6.0
Entity Framework Core 5.0 will soon be released in conjunction with .NET 5. The release is a major milestone in the long history of Entity Framework that began before version 1.0 was shipped with .NET Framework 3.5 Service Pack 1 in 2008. EF Core 5.0 is cross-platform and supports all of the most popular relational databases. It also provides a consistent API to interface with the popular NoSQL Azure Cosmos DB database. EF Core 5.0 includes scores of new features ranging from “many-to-many” and “table-per-type” to an updated migrations experience. The team is currently focused on bug fixes, updates to documentation, and planning for the next release.
The team is ready to start building the next release, but we need your help!
The Entity Framework 2020 Survey
To better understand how you work with EF Core and which features are top priority for you, the team developed this short Entity Framework survey. It will take you less than 15 minutes. Our team deeply values your feedback and sincerely hopes many of you will complete the survey. It will be open for a few weeks and we encourage you to share it with colleagues who also work with data in .NET. This is a key opportunity to help shape the next release of EF Core. We will prioritize our focus based on the responses we receive. So make sure you tell us what you want!
Here’s the link for your reference:
Thank you,
The Entity Framework Team:
@ajcvickers, @AndriySvyryd, @bricelambs, @JeremyLikness, @ShayRojansky, and @smitpatel
6 comments
More visual tools! Like modeling, etc. Microsoft was always the best in this and now I should remember bunch of looooong command-line parameters for same operation…
try to see a best offer for stevia
hi, i have used ef 4,5 and 6
i want to use ef core but it keeps giving me to many problems.
i can go back to ef 6 and the same tables in the same db work fine.
i recently tried to scaffold some tables and the code generated but at runtime it gave me an error for a non-existing relation that i could not follow, not in the code for the model so i have no idea what it did….
with errors like that how can i use it ??
Did you file an issue? The team is available to help resolve problems like this.
I don’t see Web Forms listed in the survey. I think you should go back to .NET Standard 2.0 so that it’s compatible with .NET Framework. I’m using Dapper from here on out. No more EF Core dependency hell. EF Core proved to be a total waste of time, especially after you switched to .NET Standard 2.1. That just added insult to injury.
Hi Jon,
Net standard and entity framework 6 are still very viable options for existing web forms code and net framework code. But I don’t blame Microsoft for not improving or working on web forms. It really is showing it’s age at this point.
For any new projects I would suggest asp net core or even blazor. Good luck on your projects!