I'm waiting for EF6 on .NET Core, just as you said. Once that's successfully working, and I've got all the web stuff updated to latest, then I'll look at moving EF to its latest version as well. That part scares me a bit more however, as we have hundreds of databases being managed via EF6 migrations, all at different versions (based on customer maintenance payments). We'll need to keep EF6 as a dependency as long as we want to keep updates simple and have older versions in the wild.