C# Telerik openaccess ORM 值得学习吗？

Is Telerik openaccess ORM worth learning?

提问by Rippo

I have just won 1 Telerik Premium Collection for .NET Developer with subscription (lucky me!) and was wondering whether the OpenAccess ORM is worth learning? Has anyone thrown away their open source variant and are now using the Telerik ORM tools instead?

我刚刚通过订阅为 .NET 开发人员赢得了 1 个 Telerik Premium Collection（我很幸运！）并且想知道 OpenAccess ORM 是否值得学习？有没有人扔掉他们的开源变体，现在改用 Telerik ORM 工具？

Are there any benefits from using the Telerik ORM tools instead of an open source variant?

使用 Telerik ORM 工具而不是开源变体有什么好处吗？

Any thought suggestions?

有什么想法建议吗？

BTW I can't wait to start using their RadControls for ASP.NET AJAX!!

顺便说一句，我等不及要开始使用他们的 RadControls for ASP.NET AJAX 了！！

采纳答案by ManniAT

I'm a happy telerik customer for more than 5 years. I used their ORM only in one solution and never used an open source ORM.

我是 5 年多的快乐 Telerik 客户。我只在一个解决方案中使用了他们的 ORM，从未使用过开源 ORM。

Throw away the existing one? NO - if you have no problems and the thing does what it should do I wouldn't change. That has nothing to do with quality or other aspects of telerik ORM. It's just a matter of fact that using a new product means to learn new things, solve some solved things again in a different way and so on.

扔掉现有的？不 - 如果你没有问题并且事情做了它应该做的，我不会改变。这与 Telerik ORM 的质量或其他方面无关。事实上，使用新产品意味着学习新事物，以不同的方式重新解决一些已解决的问题等等。

BUT - if you have problems (or must make compromises) with your current product it's sure worth to give it a try.

但是 - 如果您当前的产品有问题（或必须做出妥协），那么肯定值得一试。

Without knowing other ORMs I have one clear point why I would try telerik ORM. It's their (telerik's) outstanding support. None of my other vendors offers / does what telerik does. Simply take a look at their forums http://www.telerik.com/community/forums.aspxand you'll see what I mean.

在不了解其他 ORM 的情况下，我有一个明确的观点，为什么我会尝试 Telerik ORM。这是他们（telerik）的杰出支持。我的其他供应商都没有提供/做 Telerik 所做的事情。只需查看他们的论坛http://www.telerik.com/community/forums.aspx，您就会明白我的意思。

You have a problem - they solve it; and that with very fast response times.

你有问题——他们解决了；并且响应时间非常快。

And that's a point you should think about when making a decision about ORM (or any other kind of product).

这是您在做出关于 ORM（或任何其他类型的产品）的决定时应该考虑的一点。

回答by Jay Douglass

I'm one of those people that won a license at a users group meeting. Thankfully I got to experience how crappy this software is without paying for it.

我是在用户组会议上获得许可证的人之一。值得庆幸的是，我无需付费就能体验到这个软件是多么糟糕。

I never got to test the ORM capabilities because the Visual Studio integration failed. Any click on the Telerik menu in VS threw an exception. And the VS item template that was supposed to be installed was not there, so I couldn't even begin to test the functionality.

我从未测试过 ORM 功能，因为 Visual Studio 集成失败。VS 中 Telerik 菜单上的任何点击都会引发异常。而且应该安装的VS项模板也不在，所以我什至无法开始测试功能。

Don't be fooled by the pretty designer screenshots, they can't even get the installer to work correctly.

不要被漂亮的设计师截图所迷惑，他们甚至无法让安装程序正常工作。

回答by Rick B.

First off I want you to know that I am not Telerik evangelist...

首先我想让你知道我不是 Telerik 的福音传道者......

We did moved away from Telerik's ASP.NET AJAX controls only because we desired greater control over the look and feel of our UI (we still use the controls for quick internal solutions), but I must say their products are excellent given the right conditions. Our web product team started to use the Open Access ORM for our solutions and honestly we never looked back. The first reason that comes to mind to choose a Telerik solution is grade A support which has never failed to provide a resolution to a problem regarding any of their solutions with in 24hrs usually including sample code... Although I can usually dig through blogs for hours to find solutions for most of my issues regarding Microsoft technology I must say it is nice to have support when we need it.

我们确实放弃了 Telerik 的 ASP.NET AJAX 控件，只是因为我们希望更好地控制 UI 的外观和感觉（我们仍然使用这些控件来实现快速的内部解决方案），但我必须说，在合适的条件下，他们的产品非常出色。我们的 Web 产品团队开始将 Open Access ORM 用于我们的解决方案，老实说，我们从未回头。想到选择 Telerik 解决方案的第一个原因是 A 级支持，它从未未能在 24 小时内解决有关其任何解决方案的问题，通常包括示例代码......虽然我通常可以通过博客挖掘为我的大部分 Microsoft 技术问题寻找解决方案的时间 我必须说，在我们需要时获得支持真是太好了。

回答by Anthony

This is an older post, but I thought I would weigh in.

这是一个较旧的帖子，但我想我会权衡一下。

We recently started using Telerik's SiteFinity product for a client website. It is a very good, developer-oriented tool for creating a web content system without the size or expense of SharePoint or something similar.

我们最近开始为客户网站使用 Telerik 的 SiteFinity 产品。这是一个非常好的面向开发人员的工具，用于创建 Web 内容系统，而没有 SharePoint 或类似内容的规模或费用。

We also went with a Cloud solution as Telerik's ORM supports Azure, so thus so does SiteFinity - which uses OpenAccess (ORM) to communicate with its database.

我们还采用了云解决方案，因为 Telerik 的 ORM 支持 Azure，SiteFinity 也是如此——它使用 OpenAccess (ORM) 与其数据库进行通信。

I was very impressed with the speed and flexibility of it all, being my first Cloud (Azure) development project. Telerik's customer support and personal attention is beyond reproach. I have been using Telerik products for years and was not surprised how well it worked.

作为我的第一个 Cloud (Azure) 开发项目，这一切的速度和灵活性给我留下了深刻的印象。Telerik 的客户支持和个人关注无可非议。我多年来一直在使用 Telerik 产品，并且对它的工作效果并不感到惊讶。

Two days before the site was to go live everything bombed with a very inexplicable .Net error. As it turns out Microsoft announced they were upgrading their Azure SQL servers starting July, 2011: "This upgrade is also significant in that it represents a big first step towards providing a common base and feature set between the cloud SQL Azure service and our upcoming release of SQL Server Code Name 'Denali'."

在网站上线前两天，一切都被一个非常莫名其妙的 .Net 错误轰炸了。事实证明，微软宣布他们将从 2011 年 7 月开始升级他们的 Azure SQL 服务器：“这次升级也很重要，因为它代表了在云 SQL Azure 服务和我们即将发布的版本之间提供通用基础和功能集的重要第一步SQL Server 代码名称“Denali”。”

(http://blogs.msdn.com/b/windowsazure/archive/2011/07/13/announcing-sql-azure-july-2011-service-release.aspx)

（http://blogs.msdn.com/b/windowsazure/archive/2011/07/13/annoucing-sql-azure-july-2011-service-release.aspx）

By its very nature, Cloud servers are upgraded and moved around behind the scenes so you don't have to mess with it. OpenAccess failed to take this into account however, and when our SQL Azure server group was upgraded OpenAccess failed to recognize its version and bombed.

就其本质而言，云服务器在幕后升级和移动，因此您不必弄乱它。然而，OpenAccess 没有考虑到这一点，当我们的 SQL Azure 服务器组升级时，OpenAccess 无法识别其版本并遭到轰炸。

Telerik, of course, was very quick about releasing a patch - but it still took them a few days. We couldn't wait that long, unfortunately, having already lost quite a bit of time just trying to figure out what was going on. The practical result was that I got to work nonstop for two days with no sleep to move the whole thing into a regular .Net solution with Entity Framework 4 as the ORM.

当然，Telerik 很快就发布了补丁——但他们还是花了几天时间。不幸的是，我们不能等那么久，我们已经失去了相当多的时间只是想弄清楚发生了什么。实际结果是，我连续两天不眠不休地工作，将整个事情转移到以实体框架 4 作为 ORM 的常规 .Net 解决方案中。

So to answer the question: Is Telerik ORM worth learning and / or better than an open source solution? I agree with the above statement that if you already have an open source solution, it is working well, has good performance, and is intuitive to develop against - absolutely stick with that.

所以要回答这个问题：Telerik ORM 值得学习和/或比开源解决方案更好吗？我同意上面的说法，如果你已经有一个开源解决方案，它运行良好，性能良好，并且开发起来很直观——绝对坚持。

The value of open source is the community that supports it and your ability to make changes to the underlying system if need be. Had my project been based on an open source ORM, I could have changed the code to default to the most recent version of SQL if it finds it is working with a version higher, and problem solved - sleep had.

开源的价值在于支持它的社区以及您在需要时对底层系统进行更改的能力。如果我的项目基于开源 ORM，我可以将代码更改为默认为最新版本的 SQL，如果它发现它正在使用更高版本的 SQL，并且问题已解决 - sleep had。

The value of a product like OpenAccess ORM is that it is in competition with other products, open source or otherwise, and it has to: Perform Well, be customer oriented, have a manual (very important), and be easier than doing it yourself or learn an open source system that may or may not be very intuitive.

像 OpenAccess ORM 这样的产品的价值在于它与其他产品、开源或其他产品竞争，它必须：表现良好、以客户为导向、有手册（非常重要）、比自己做更容易或者学习一个可能非常直观也可能不太直观的开源系统。

Throw in that Telerik's support is top notch, and I would say you could do worse - as long as you are willing to give up some control and have to wait for upgrades / patches to handle things like I described above.

加上 Telerik 的支持是一流的，我想说你可以做得更糟 - 只要你愿意放弃一些控制权并且不得不等待升级/补丁来处理我上面描述的事情。

回答by Lance Parkington

I would certainly recommend using the Telerik Open access ORM. I have used Telerik products (eg telerik Ajax/Silverlight) for a number of years and they are best in class and the technical support is second to none. The company makes money by providing software that works.

我当然会推荐使用 Telerik Open access ORM。我已经使用 Telerik 产品（例如 Telerik Ajax/Silverlight）很多年了，它们是同类产品中最好的，技术支持也是首屈一指的。该公司通过提供有效的软件来赚钱。

Unfortunately this does not apply to open source since by definition anything can changed without proper control. All it needs is one duff developer and an entire suite can be rendered useless.

不幸的是，这不适用于开源，因为根据定义，如果没有适当的控制，任何事情都可以改变。它所需要的只是一个笨拙的开发人员，整个套件都可以变得毫无用处。

In order to use the products correctly, swiftly, and efficiently, it is necessary to be a highly competent web developer.

为了正确、快速、高效地使用产品，必须成为一名高素质的 Web 开发人员。