3 ms·
And Entity Framework Core unfortunately because EF6 was already a thing.
by vyrotek 5y ago
And Entity Framework Core unfortunately because EF6 was already a thing.
- WorldMaker 5y agoYeah, hopefully as others have pointed out, with .NET 7 next year all the version numbers align so that ASP.NET and EF can drop "Core" again.
- foepys 5y agoSearching the internet for help is going to be a nightmare, though.
- WorldMaker 5y agoShouldn't be too bad, I don't think, if you remember the version number. Which anyone that worked in ASP.NET 4, 5 or 6 was generally pretty used to (a lot of things changed between versions even the "classic" .NET Framework days). I still have "fond" memories of fighting to find a specific EF6 answer that was different from EF4 or EF5, but that was still somewhat easier than having to remember to add "core" to all your searches lest you get classic EF3 results when searching for EF Core 3.x help. Having a version number high enough that you no longer need "core" is something I'm looking forward to.
- svick 5y agoI guess they could do that, but what makes you think they actually will?
- WorldMaker 5y agoI stated "hopefully … they can". I mangled the commas on that one, but that was the intended statement: "hopefully they will". I have no idea if they actually will.
- yyyk 5y agoThere was an EF7 RC1 version, and .NET 7 isn't LTS. Dropping "Core" is better done in .NET 8 - or MS could pick an entirely new name.