What does your company use to access and map the database? Does it make you happy or sad?

Question

I started working in a medium-sized financial firm, and everything was done using home-based ORM. I recently moved to an online store, and this is a combination of ADO.NET and linq with sql. I wonder what other people use in their stores and why? Are you satisfied with this or want you to use a different approach?

• Do it yourself using ADO.NET (sqlconnection, sqlcommand)
• linq to sql
• entity structure
• nHibernate (or other non-Microsoft ORM)

I am not trying to start a fiery war. This question is not about whether EF or nHibernate is the best ORM, it's just what you use in your company. I think it’s interesting to know what other people use in the real world.

Answer 1

I work in the SQL Server team at Microsoft, and a recommendation in the future is to use the Entity Framework on Linq to Sql or ADO.net (this is not my job to speak for the company though, so do not take this as the final official word).

Personally, I have used ADO.net and LINQ to SQL in my projects so far (a lot of legacy code), but I think that Linq to SQL is much nicer than ADO.net, and from what I have learned about the Entity Framework , it is even more powerful and convenient to use, so I will use it for all future database development.

Answer 2

2 . , "Do-it yourself using ADO.NET" , LINQ to SQL , 2008 ADO.Net , , EF L2S , EF, Microsoft EDM. , Microsoft L2S , , L2S , Microsoft EF L2S .
nHibernate - "" EF, , , nHibernate, , . , , , EF - , 2- , nHibernate - ORM, Java Hibernate, .

Answer 3

, , , , , , .. , , ... , , ...

, !