4 ms·

In my case, I'm waiting for EntityFramework to catch up before switching most legacy applications over. I've been using standard 2.0 for new projects since it

In my case, I'm waiting for EntityFramework to catch up before switching most legacy applications over. I've been using standard 2.0 for new projects since it became available and building for dual deployment, either with Heroku or as a Windows service. There's definitely a crowd of .net devs that doesn't care. They're probably not the ones on HN though. I've been holding my breathe waiting for all the libraries to catch up. We're so close! I actually moved to .NET by choice for the Nemerle language a long time ago (C# mostly caught up, so I switched over). I might not be representative of everyone, but there's at least a subset of developers eagerly waiting on some small thing which will let them make the jump.

WorldMaker 7y ago
EF Core has caught up a lot in 3.x. It's LINQ support is now possibly better than EF ever was, especially with the move to the new "throw an error if the query provider can't do it" model where "downgrades" from SQL to in memory operations must be explicit now (such AsEnumerable() calls). EF (not-Core) 6.3 has also been finally ported to .NET Core (though I think it is still considered "Preview" quality) which should be directly plug and play for some types of legacy applications (Microsoft seems hopeful it will mean more WinForms and WPF apps will just run on .NET Core now).
- caseymarquis 7y ago
  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.

WorldMaker 7y ago

EF Core has caught up a lot in 3.x. It's LINQ support is now possibly better than EF ever was, especially with the move to the new "throw an error if the query provider can't do it" model where "downgrades" from SQL to in memory operations must be explicit now (such AsEnumerable() calls). EF (not-Core) 6.3 has also been finally ported to .NET Core (though I think it is still considered "Preview" quality) which should be directly plug and play for some types of legacy applications (Microsoft seems hopeful it will mean more WinForms and WPF apps will just run on .NET Core now).

caseymarquis 7y ago
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.