devart dotConnect MySQL

发布于 2024-08-14 04:09:26 字数 330 浏览 5 评论 0原文

我一直在评估 MindScape Lightspeed 的模型创建目的。到目前为止我很满意。我进一步寻找 OOTB(实际上是一些专业质量代码)提供商的 MySQL for ASP.Net。我遇到了 Devart 的“dotconnect for MySQL”。这看起来符合后一个要求。它还具有用于创建实体模型的“实体开发人员”(我发现这个有点晚了)。不过我还没有对此进行评价。我当然想继续使用 dotconnect 来使用各种提供程序,但我不确定 Entity Developer 与 MindScape Lightspeed 相比有多好。这个问题源于这样一个事实:我是一家非常(准备非常非常)的小店,我想明智地投资,即使是 100 美元的事情。

I've been evaluating MindScape Lightspeed for the purpose of Model creation. So far I am satisfied. I was further looking for OOTB (actually some professional quality code) providers for MySQL for ASP.Net. I've come across 'dotconnect for MySQL' from Devart. This looks like fitting the bill for the latter requirement. It also has 'Entity Developer' for creating Entity Models (I discovered this a little late). I have however not evaluated this. I surely want to go ahead with dotconnect for the purpose of using various providers but I am not sure how good Entity Developer is in comparison to MindScape Lightspeed. This question stems from the fact that I am a very (ready as very very) small shop and I would like to invest smartly even if it is a matter of $100.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

橘香 2024-08-21 04:09:26

首先,我为 Mindscape 工作 - 只是为了了解情况:-) 我不是 devar 客户,也许有人可以添加其他信息(如果他们使用过他们的工具)。要说明您正在查看的产品:

Entity Developer - 用于创建模型的设计器工具。它允许您生成 LINQ to SQL 或 LINQ to Entities 的模型。 Microsoft 已经提供了设计人员来执行此操作,但是 devart 提供的工具似乎更优秀,如果您对默认工具有问题,则可能物有所值。

dotconnect for MySQL似乎是一个让实体框架与 MySQL 对话的提供程序。默认情况下,实体框架不提供此功能,但提供了一个插件框架,以便开发人员可以构建提供程序(在本例中为 MySQL)。我在这里可能是错的,但看起来就是这样。这意味着 ORM 因素由 Microsoft 控制,您将拥有 Microsoft 规定的功能和发布周期(这可能是好事也可能是坏事,具体取决于您的要求:-)

LightSpeed 是 Mindscape 开发的一个底层 ORM。除了将我们的设计器集成到 Visual Studio 之外,它没有重复使用 Microsoft 技术。这意味着我们响应请求的能力优于微软。我们已经支持 MySQL 以及许多数据库,这意味着如果您购买 LightSpeed 并随后使用不同的数据库引擎执行另一个项目,则无需购买其他产品。我们发布了一份粗略的有关 LightSpeed 和实体框架之间的根本差异的指南 在我们的 orm 比较文档中(注意:它是基于与 .NET 3.5 提供的实体框架的比较,而不是明年发布的实体框架)。

就设计师而言,我不确定他们的详细比较如何。 LightSpeed 设计器 长期以来一直支持架构往返(这意味着如果您在设计器中更改模型,您可以将更改推送到数据库,或者如果您更改数据库,您可以右键单击并根据数据库更改更新模型 - 无论对您有用)。通过我们今天发布的 LightSpeed 3.0,我们还自动跟踪迁移,以便您在发展解决方案时无需手动创建 SQL 文件来迁移数据库架构。如果您希望更改生成代码的模板,欢迎您这样做 - 这看起来与 devart 设计器允许的类似。

话虽如此,如果您正在寻找 Visual Studio 对基本 ASP.NET 控件(如表适配器)的支持,那么您可能会发现 devart 产品是更好的选择,因为它可以更好地呈现此类内容。在大多数情况下,从技术上讲,您可以通过使用 ObjectDataSource 包装 LightSpeed 实体来使用 LightSpeed,但这是一个额外的步骤。

总的来说,我可以理解这些产品看起来很相似,但实际上同时却有很大不同。我没有列出优点和缺点,因为这绝对取决于您正在寻找什么以及您正在构建的项目类型。当您了解更多信息时,我感谢您的反馈 - 让我知道您的发现:-)

另外 - 如果您还有任何其他问题,或者如果您想更详细地讨论您的要求,请使用联系表我们的网站 - 我很乐意提供帮助!

First off, I work for Mindscape - just to get the disclosure of the way :-) I'm not a devart customer and perhaps somebody could add additional information if they've used their tools. To state what the products are you're looking at:

Entity Developer - a designer tool for creating a model. It allows you to generate a model for LINQ to SQL or LINQ to Entities. There are already designers provided to do this by Microsoft however the tools provided by devart appear to be superior and may be worth the price if you have issues with the default tools.

dotconnect for MySQL appears to be a provider that lets the Entity Framework talk to MySQL. By default the Entity framework provides no capability for this but does provide a plugin framework so that developers can build providers (in this case, MySQL). I could be wrong here but that's how it looks. This means the ORM factor is controlled by Microsoft and you would have the capabilities and release cycle dictated by Microsoft (this can be a good or bad thing depending on your requirements :-)

LightSpeed on the other hand is a ground up ORM that Mindscape have developed. It does no re-use Microsoft technologies other than integrating our designer into Visual Studio. This means our ability to respond to requests is superior to that of Microsoft. We have baked in support for MySQL as well as many databases meaning if you purchase LightSpeed and later do another project using a different database engine you won't need to purchase another product. We have published a rough guide to the underlying differences between LightSpeed and the Entity Framework in our orm comparison document (note: it's based on comparing to the Entity Framework delivered with .NET 3.5, not the one coming out next year).

In terms of the designer, I'm not sure how they compare in detail. The LightSpeed designer has supported schema round tripping for a long time (meaning if you change the model in the designer you can push changes to the database OR if you change the database you can right click and update the model based on the database changes - whatever works for you). With LightSpeed 3.0 which we released today, we also auto track migrations so that you do not need to manually create SQL files to migrate your database schema as you evolve your solution. If you wish to alter the templates for the generated code you are welcome to do so - which seems similar to what the devart designer allows.

Having said all this - if you're looking for Visual Studio support for the basic ASP.NET controls (like table adapters) then you would likely find a better bet with the devart product because it surfaces that sort of thing better. You can technically use LightSpeed with these by wrapping LightSpeed entities with an ObjectDataSource in most cases but it's an additional step.

On the whole, I can appreciate that the products appear similar-ish but are actually quite different at the same time. I haven't listed out pro's and con's because it absolutely depends on what you're looking for and the type of project you're building. I appreciate your feedback as you find out more - let me know what you discover :-)

Also - if you have any further questions or if you'd just like to have a chat about your requirements in more detail please use the contact form on our website - I'm happy to help!

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文