Which ORM should i be using for .Net in 2016 to talk to SQL server?

.net asp.net entity-framework linq orm


I don't yet have a deep understanding of.Net because most of my server side experience has been with nodeJS, meteor, or rails. Because ActiveRecord appears to be the only ORM solution available in Rails, criticizing it is rather simple. My strategy was to use the ORM to query whatever you could and fall back to raw SQL if you couldn't.

I'm unsure of the future's direction as I try to read tutorials and classes on accessing databases in.Net 4.5 or newer projects. The following are tutorials that I observe

  • Lambda syntax in Linq
  • Query syntax in Linq
  • Enterprise Framework

What recommended ORM is there for contemporary.net apps? All of the aforementioned appear to allow me to perform simple CRUD tasks. But which one would be more appropriate for, say, table joins? Mind you, for my.net solutions, I only ever intend to run queries on Microsoft SQL server databases.

Reading that EF used linq in addition to having it replaced by EF greatly perplexed me. Therefore, I am unsure about whether I am using a past or future tense syntax when I read an example that says pick all columns. I can't determine if the code is linq or EF just by looking at it. However, I can identify whether it is lambda or query syntax.

5/12/2016 2:31:40 PM

Accepted Answer

8/21/2017 2:09:06 AM

Popular Answer

Entity Framework is the quick answer.

You may be perplexed by the fact that Entity Framework supports the Linq Lambda and Linq Query syntaxes. But Fluent API, in my opinion, is the way of the future.

Entity Framework 7 (pre-release) seems to be concentrating on Fluent API, based on my experience of it. Which is great with me because I prefer it to Linq syntax by a wide margin.

Related Questions


Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow