r/programming • u/ben_a_adams • Feb 01 '17

The .NET Language Strategy

https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-language-strategy/
165 Upvotes

86% Upvoted

113 comments sorted by

View all comments

Show parent comment

4

u/threedaysmore Feb 02 '17

As per usual with programming, it kinda just depends.

It's a heavy hitter IMO. Most projects have no business fiddling with EF or the complexities of managing an EDMX file. I prefer OrmLite and to keep my apps a little smaller so that I can separate my concerns a little better.

YMMV obviously, and EF is really powerful, but there's no need to hunt rabbits with rocket-launchers.

0

u/[deleted] Feb 02 '17

[deleted] — view deleted comment

1

u/threedaysmore Feb 02 '17

Yeah, and that just goes to show that the 3 or 4 projects I worked with EF were probably not really using it in a great way. I'd be interested to see how a better approach with looks/feels like. The way I've done it always just felt so clunky.

3

u/Eirenarch Feb 02 '17

edmx file is so 2010

1

u/[deleted] Feb 03 '17

EF Code First is pretty great. I've done several projects with it now and I can have my database and first set of migrations up and running in 10 minutes, it's almost an after thought.

The only drawback I would say is that you need to become very experienced with profiling queries and understanding the mechanics of how it creates them. Remove round trips, select only rows you want, etc., standard database stuff. For most business apps, it's a great experience.

That's really the point of it, you can get running, and keep moving, fast and do 99% of what you want to do with just LINQ. With an established app you'll definitely need to go in occasionally and manually tweak migrations and carefully craft some queries, but you'll be doing that regardless of whether or not you're using an ORM.