Telerik OpenAccess ORM - 有人使用它吗?
我现在正在开发一个新项目,并且正在考虑使用 Linq to SQL 之外的 ORM。我目前已将 Linq to SQL 连接到存储库中,但我不喜欢我的存储库必须与我的数据库结构相匹配的方式。 (示例:我在用户和 OpenID 之间有一个联接,我需要 2 个类(每个表一个)和一个用于联接它们的视图的类)。
我听说过有关 Telerik 的 OpenAccess ORM 的一些好消息,并且我确实拥有它的许可证(尽管已经过时 - 最新版本:2009.1 405(2009 年 4 月 5 日))
我的问题是...
有人使用过它吗?
学习曲线如何?
对于我的上述场景来说,它是一个好工具吗?
我的版本是否可以,无需更新我的许可证?
I'm working on a new project right now and am thinking of using an ORM beyond that of Linq to SQL. I've currently got Linq to SQL wired up into a repository, but I'm not loving the way my Repo has to match my DB structure. (Example: I have a join between Users and OpenID's, and I need a 2 classes ( one for each table) and a class for the View that joins them).
I've heard some good things about Telerik's OpenAccess ORM and I do have a license for it (though outdated - Latest Version: 2009.1 405 (Apr 5, 2009))
My questions are...
Has anyone used it?
How is the learning curve?
Is it a good tool for my above scenario?
Is the version I have ok without having to update my license?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我们公司是一家价值 2.5B 美元的太阳能制造公司。当我们开始设计所有应用程序所基于的应用程序框架后端 v2 时,我们研究了 Telerik ORM。我花了几周时间看它。我们的结论是,它太复杂,而且有点不稳定,无法满足我们的需求。我们选择了 L2S,并且没有后悔。 L2S 提供了我们需要的所有功能,并且简单直接。在我看来,微软在实体框架上花费了如此多的资源,这太糟糕了,因为他们在 L2S 领域有一个赢家。
Our company is a $2.5B solar manufacturing company. When we started designing v2 of the application framework backend that all our applications would be based on, we took a look at the Telerik ORM. I spent a couple weeks looking at it. Our conclusion was that it was too complex, and a little flaky, for our needs. We went with L2S and have not regretted it. L2S has provided all the capabilities we need and is simple and straight forward. IMO, it's too bad Microsoft is spending so many resources on Entity Framework, because they have a winner in L2S.