blocks|key|486383|text|要问自己的一个重要问题是，您是否可以接受对SQL+Server的依赖关系。例如，数据库后端是否会更改为Oracle？LINQ+to+SQL与SQL+Server是强耦合的，而NHibernate并非如此，我并不是说这是一个很糟糕的限制，但考虑到这一点很重要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|486384|在过去的几年里，NHibernate确实取得了长足的进步。例如，我真的很喜欢流畅的NHibernate，但这并不是说LINQ+to+SQL是有限的。我喜欢与Visual+Studio的集成，它已经证明了自己完全有能力处理一致的负载(例如，Stack+Overflow使用LINQ+to+SQL+)。|486385|与普遍的看法相反，LINQ+to+SQL+is+not+dead。|offset|length|486386|编辑：要问自己的另一个重要问题是，您是否想要更改域模型。LINQ+to+SQL将对象直接映射到表。另一方面，NHibernate允许间接层。顺便说一句，实体框架也是如此。|style|BOLD|486387|entityMap|0|LINK|mutability|MUTABLE|url|http://geekswithblogs.net/michelotti/archive/2009/11/10/linq-to-sql-again.aspx^0|0|0|9|N|0|0|0|3|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@$F|10|G|11|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

One important question to ask yourself is if you can accept a dependency on SQL Server. Will the database backend change to Oracle, for example? LINQ to SQL is strongly coupled to SQL Server, whereas NHibernate isn't. I'm not saying that this is necessarily a bad limitation, but it's important to consider.

NHibernate has really come a long way in the past few years. I really like Fluent NHibernate, for example, but that's not to say that LINQ to SQL is limiting. I love the integration with Visual Studio and it has proved itself more than capable of handling consistent load (Stack Overflow uses LINQ to SQL, for example).

Contrary to popular belief, <a href="http://geekswithblogs.net/michelotti/archive/2009/11/10/linq-to-sql-again.aspx" rel="nofollow noreferrer">LINQ to SQL is not dead</a>.

Edit: Another important question to ask yourself is if you want to change the domain model. LINQ to SQL maps objects directly to tables. NHibernate, on the other hand, allows for a layer of indirection. This is also true of Entity Framework, by the way.

blocks|key|509528|text|我会选择NHibernate，因为有一个很好的开源社区支持它，回答有关它的问题，等等。当您的产品变得更大、更复杂时，您将会欣赏到NH的强大和灵活性。最后，Linq-+to+-sql不在MS的长期计划中，因为他们希望您使用Entity+Framework，因此您可能会在那里使用一种死胡同的技术。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|509529|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'd go with NHibernate, because there's a nice open source community out there that supports it, answers questions on it, and so on. As your product gets bigger and more complicated, you'll appreciate the power and flexibility of NH. Finally, Linq-to-sql isn't in MS's long term plans, since they want you to use the Entity Framework, so you might end up with a dead-end technology there.

blocks|key|486242|text|如果您没有使用ORMs的经验，那么Linq+to+SQL比NHibernate更容易学习。它还与Visual+Studio进行了更好的集成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|486243|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you don't have experience with ORMs Linq to SQL is slightly easier to learn than NHibernate. It also has better integration with Visual Studio.

blocks|key|1811188|text|我会投票支持Linq-to-SQL+-为什么？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1811189|something|1811190|NHibernate+|unordered-list-item|1811191|它有一个可视化的设计器，可以让你更容易、更快地获得结果，并看到something|1811192|NHibernate非常强大-但这也让它更难学；你必须真的喜欢尖括号汤(即大量的映射文件)才能快速使用NHibernate|1811193|1811194|1811195|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|S|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

I would put in my vote for Linq-to-SQL - why?

<ul>
<li>it has a visual designer which allows you to more easily and quickly get results and see something</li>
<li>NHibernate is very powerful - but that also makes it harder to learn; you have to really really love angle bracket soup (i.e. lots of XML mapping files) to get up to speed with NHibernate</li>
</ul>

blocks|key|1809227|text|我喜欢Linq+to+SQL，它非常容易使用。实现存储库模式，并使用LINQ+to+SQL作为存储库接口后面的第一个实现。你会发现使用这个工具可以很容易地快速建立一个存储库。您始终可以使用NHibernate实现第二个存储库，而不会破坏您的应用程序，然后比较您使用这两个工具的体验。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1809228|NHibernate更“强大”……我猜这意味着你可以对任何数据库使用它，仅此而已。还有很多东西需要学习，如果你真的走了那条路，请确保充分利用流畅的NHibernate，以避免所有的映射垃圾。有一大堆XML映射要维护，这要干净得多。|1809229|我发现NHibernate令人沮丧，因为我喜欢用LINQ查询数据库并将其映射(映射)到模型。我知道有一个LINQ+to+NHibernate到处流传，但我不知道有谁在使用它。|1809230|一般来说，如果您乐于通过ID获取所有内容并从那里遍历对象模型，我会说使用NHibernate。一旦你想要执行更复杂的查询，你最好准备好面对一些挫折。|1809231|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I love Linq to SQL, it's very easy to use. Implement the repository pattern and use LINQ to SQL as your first implementation behind your repository interface. You'll find it's so easy to get a repository up quickly using the tool. You can always implement a second repository using NHibernate without breaking your app then compare your experience with the two tools.

NHibernate is "more powerful"... I guess that means you can use it against any database, and that's about it. There's a lot more to learn and if you do go that route, make sure you make full use of Fluent NHibernate to avoid all the mapping rubbish. It's much cleaner that having a bunch of XML mappings to maintain. 

I find NHibernate frustrating becuase I like querying the database with LINQ and projecting (mapping) to a model . I know there is a LINQ to NHibernate floating around, but I can't say I know anyone who uses it. 

Generally, I would say to use NHibernate if you are happy to get everything by ID and traverse the object model from there. As soon as you want to execute more complex queries you had best be prepared for some frustration.

blocks|key|509848|text|Linq+to+SQL应该被实体框架取代；我认为NHibernate会是一个很好的选择，因为有很多参考资料，而且它似乎也被广泛使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|509849|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Linq to SQL is supposed to be replaced by the Entity Framework; I think NHibernate would be a good choice since there are lots of references and it seems be widely used as well.

blocks|key|1811114|text|除了Darin+answer之外，请考虑我之前读到的这篇文章。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1811115|Linq+to+SQL更容易、更快地实现和快速集成，但如果您需要更多控制，Nhibernate可以为您提供更大的灵活性。最近，我不得不决定是否在我的新应用程序项目中使用Linq+to+SQL+-我只是不喜欢缺乏灵活性。|1811116|NHibernate+vs+LINQ+to+SQL+http://www.acceptedeclectic.com/2007/12/linq-to-sql-vs-nhibernate-part-1-what.html|offset|length|1811117|如果有帮助，请告诉我。|1811118|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/26971/nhibernate-vs-linq-to-sql|1|http://www.acceptedeclectic.com/2007/12/linq-to-sql-vs-nhibernate-part-1-what.html^0|0|0|0|P|0|Q|2A|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]|$F|Z|G|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

In addition to Darin answer, Consider this post i read earlier. 

Linq to SQL is easier and faster to implement and integrate quickly, but Nhibernate can give you more flexibility if you need more control. Recently, i had to decide if i was to use Linq to SQL on my new app project - i just didn't like the lack of flexibility.

<a href="https://stackoverflow.com/questions/26971/nhibernate-vs-linq-to-sql">NHibernate vs LINQ to SQL</a>
<a href="http://www.acceptedeclectic.com/2007/12/linq-to-sql-vs-nhibernate-part-1-what.html" rel="nofollow noreferrer">http://www.acceptedeclectic.com/2007/12/linq-to-sql-vs-nhibernate-part-1-what.html</a>

Let me know if it helps.

I want to learn ORM and I wonder which is beneficial for start up; Linq to SQL or Nhibernate. considering time,adaptation... etc

Which is beneficial for start up; Linq to SQL or Nhibernate?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想学习ORM，我想知道哪个对启动有利；Linq to SQL还是Nhibernate。考虑到时间，适应能力...等

问哪个对启动有利；Linq to SQL还是Nhibernate？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问哪个对启动有利；Linq to SQL还是Nhibernate？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问哪个对启动有利；Linq to SQL还是Nhibernate？
EN