Missing Features in Entity Framework Core

15 Comments

• Dang... seems like a damning list. :( I was thinking about getting involved with this for my next project but I might stick with 6.0...
  

• Hi, Mike!
  Yeah... even MS warns that the 6.x version is the recommended one... It's gonna take some time, I guess. Some of these are must-have features - just take the GroupBy thing, for instance.
  

• No Group by and no datetime operations? These two features alone are a reason to stay as far away from EF Core as I can!!! I would love it if I could use EF Core for a current project, but the current state makes it imposible. And probably at least for the next year too.
  

• Raul: totally understand you, I feel the same. EF Core is not ready for production.
  

• I loved Data Annotations validations using partial meta classes. I don't remember using EF specifically for validation, so I assume JS/MVC model validation will continue to work as-is.
  

• Mycall: yes, here I'm talking about validations on the DbContext, when it goes to SaveChanges.
  

• Yes, indeed. What's striking is how this continues to be a challenge for the group that has worked on this for over a decade now. Even with a rewrite it has proved to be a daunting undertaking. I've been with them since the start and have followed them from the beginning (and am one of their biggest fans), so it's been interesting to follow.
  
  This is still a disappointment, however. I am looking at building a new app (my first) and was hoping to use EF Core. Hopefully I can find a solution to use EF6.0 on the server, while still using something viable on my (Xamarin/UWP) clients. Definitely open to any suggestions. :)
  

• Wow, how can you guys seriously consider this a production ready release without even BASIC date functionality? This tells me that EF Core simply isn't ready. As far as I can tell there is A LOT of heavy lifting that needs to be done before you guys should consider a 1.0 release.
  

• TheLievense:
  Who are "you guys"? I totally agree with you! :-)
  

• SQLite does not support transactions around schema changes, and so migrations are pretty much crippled on Android and IOS (Xamarin). Not really an EF Core problem but a showstopper for me.
  

• This link is wrong´: https://github.com/aspnet/EntityFramework/issues/1186 should be: https://github.com/aspnet/EntityFramework/issues/5837
  
  Also, would be nice with an update for 2.0 preview1:
  Filters (reduces need for query interception, but not mentioned directly in your list)
  Owned entities (Complex Types)
  https://github.com/aspnet/EntityFramework/issues/2805 - fixed
  https://github.com/aspnet/EntityFramework/issues/2850 - groundwork done
  https://github.com/aspnet/EntityFramework/issues/246 - done
  
  

• Hi, ErikEJ!
  Thanks, you are right, I updated the link.
  As for the stuff that will be fixed in EF 2.0, I will write another post, when it is released.
  Cheers!
  

• Hard to read the table, please consider adding horizontal lines for each row.
  

• This list needs to be updated:
  https://blogs.msdn.microsoft.com/dotnet/2018/05/30/announcing-entity-framework-core-2-1/#comment-542395
  

• Thanks, Mohammad! Indeed it does! ;-)