The big news last week was that the ASP.NET 5 & EF7 stacks were renamed in an attempt to alleviate the confusion around the naming of everything under the ASP.NET 5 umbrella.
ASP.NET 5 is now ASP.NET Core 1.0
EF7 is now EF Core 1.0
The naming has been a topic of debate since each of these were introduced by Microsoft and throughout their development. The teams finally accepted that the myriad questions and complicated answers about the naming in the ASP.NET 5 stack was enough of a red flag to change the names. While it is a huge relief to many, the timing is problem for people who have invested in asp.net 5 already because the name is not just a brand but it will affect packages as well. As per the announcement on github
Microsoft.AspNet.*packages and namespaces are changing to
EntityFramework.*packages and namespaces are changing to
- The version numbers of all of the above are being reset to
Changing the namespaces this late in the game is going to be painful for devs/companies who have already been building apps and tooling on ASP.NET 5 &/or EF7. We are already on RC1 which was released in November with a go live license. Rick Strahl has a great [balanced] post talking about this.
Other than this, both ASP.NET Core & EF Core will move forward as planned. RC2 is supposed to be out sometime in February and they remain committed to the initial RTM at the end of March.
Here are the new namespace names for EF Core for RC2, as per https://github.com/aspnet/EntityFramework/tree/dev/src
|In EF7||In EF Core|
If you are curious about what’s in EF Core, check out my EF7 Course on Pluralsight which I created during the Beta 4 …then read my recent post, EF7 Updates and Changes on Pluralsight’s blog which takes you from there to the current RC1.
Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!
7 thoughts on “EF7 is now EF Core 1.0, Package and namespaces change too”
Thanks for the news! Didn’t know they renamed it!
BTW, changing namespaces shouldn’t be THAT problematic, should it? I mean, could it hurt to do a massive search and replace?
Pardon my ignorance.
Trying to merge a VS/2013 MVC6 project into aspnet5/EF7/mvc project (via: yo aspnet)
I’m having trouble with the Fluent API in EF7 (rc1-final) setting up many to many relationships in my domain model. (.WithMany not recognized)
Seeing as EF7 is being detoured to EF Core 1.0, should I be brave and start with the cli-samples/HelloMvc and port around that or hunt down EF7 nightly builds?
Am I the only one awaiting the good folks at OmniSharp to update generator-aspnet to support .rc2/dotnet? I think not…