实体框架VS替代品 [英] Entity Framework vs alternatives

问题描述

复制：

• What针对.NET ORM框架你最喜欢？


• 什么是你目前正在使用的数据访问？


• When选择一个ORM，是的LINQ to SQL或LINQ到实体比NHibernate的好？


• Database （和ORM）为中小型.NET应用程序的选择


• 等等

• What ORM frameworks for .NET Do You Like Best?
• What are you currently using for data access?
• When choosing an ORM, is LINQ to SQL or LINQ to Entities better than NHibernate?
• Database (and ORM) choice for an small-medium size .NET Application
• Etc.

你会推荐一个大的ASP.NET应用程序，实体框架或NHibernate的什么，或者\\米你认为什么具体到这两种技术的优点和缺点？

What OR\M would you recommend for a large ASP.NET application, Entity Framework or NHibernate. What do you consider to be the advantages and disadvantages specific to both technologies?

推荐答案

我一个相当漫长的答案放在一起，一个类似的问题：<一href=\"http://stackoverflow.com/questions/349718/ado-net-entity-framework-decision-making-between-orm-solutions/349755#349755\">ADO.NET实体框架：ORM解决方案的之间的决策。

I put together a fairly lengthy answer to a similar question: ADO.NET Entity Framework: Decision Making between ORM solutions.

不过，既然你问:)我同意，我会选择NHibernate的一个企业网络解决方案的今天，但是..

However, since you asked :) I agree, I'd pick NHibernate for an "Enterprise" web solution today, however..

实体框架的下一个版本应该是值得考虑在很长的很难看。第一个版本是没​​有准备好大规模部署和生成的T-SQL极不理想很多，但我看到了光明的未来，如果ADOEF球队能够正确地放在一起。这可能是真正的东西，尤其是如果它能够消耗重组后的SQL数据服务！

The next version of the Entity Framework should be worth taking a long hard look at. The first version wasn't ready for large scale deployment and the generated T-SQL leaves a lot to be desired, but I see a big future if the ADOEF team can put it together correctly. It could be really something, especially if it's able to consume the revamped SQL Data Services!

如果有的话，我会刷上ESQL（实体SQL）和习惯的语法使用LINQ to写入数据的查询。东西告诉我，这将是很好的经验有得心应手未来几年。

If anything, I'd brush up on eSql (Entity SQL) and get used to the syntax for using LINQ to write data queries. Something tells me this will be excellent experience to have handy for the next few years.

这篇关于实体框架VS替代品的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！