Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 12 years ago.

Dapper ,和 PetaPoco 。我在PetaPoco对Dapper、Masive和POCO的支持是简单明了的,但目前拖延了谁选择下一个项目。

我确实知道,在很大程度上,它涉及的是个人信条,但认为听取关于这个主题的一些意见是很有价值的,特别是来自那些尝试其中不止一个图书馆的人(is)。正确术语:图书馆、档案、框架?

Answer 1

决定你提到哪些特点——简明扼要、灵活、支持——从现在起,对你和你的项目()最为有用。哪些工作最有可能使你的工作更容易?

然后,请你回答。如果你仍然可以选择的话,请Dapper(作随机选择,我做过:-) 正如切希尔·卡塔所说,如果你不真正知道你想要去哪里,那就没有你选择的道路。

Answer 2

PetaPoco s documentation seems more mature than others. It seems like it is the safest route.

Answer 3

i havent triend any of those. by default i always base my decision on number of lines of resulting client code and type safety. of course there are number of other metrics you should take into account but if your project is not constrained by any special (exotic) requirements those two are generally appliable. btw. i am aware about controversy my response may lead to ;)

友情链接