4 ms·
I'm the lead developer on a startup and all of our backend code is .net core (the frontend is still 4.5)! I love it. Feel free to PM for more info.
by jmkni 10y ago
I'm the lead developer on a startup and all of our backend code is .net core (the frontend is still 4.5)!
I love it.
Feel free to PM for more info.
- DaiPlusPlus 10y agoDo you use EF at all? I'm interested in DNX but only EFC works on DNX, not EF6, and EFC is missing so much necessary functionality (Lazy-loading, Linq joins, Complex types, etc) it's a total no-go for the projects I do that all tie-in with databases.
- flukus 10y agoHave you looked into nHibernate's support for .net core? It was always more flexible than EF anyway, I've been watching EF slowly fix their design mistakes to be more like nHibernate since version 1.
- DaiPlusPlus 10y agoI haven't. I've been "loyal" to EF since the LinqToSql days, though I did use NHibernate heavily about 10 years ago. My main draw is the quality of the tooling and the nice EDMX model designer. The other draw is Linq support for compile-time type-safe queries (which I've noticed are compiled into good SQL with less mangling than I'd expect). I am guilty of not staying on top of trends outside the MS camp. I does NHibernate now offer parity with EF? I just don't want to write SQL/HQL in strings.
- flukus 10y agoI think it has full linq support now (although could be wrong), but it's had type safe queries for many years now, almost as long as .net has had lambda expressions. It's very much like using EF without linq and just using the .Where syntax. I've used it on some projects that never had any HQL (which is an abomination). There are also a bunch of stuff like future queries that could make it much more performant than EF.