微软是否确认了他们对 LINQ to SQL 生命周期终结的立场?

问题描述

我正在尝试就我负责移植到 MVC 2 的许多遗留应用程序使用什么 ORM 做出明智的决定.我看过的 ORM 是 LINQ to SQL、LINQ to Entities 和 nHibernate.L2S 似乎是最简单的，但我发现许多文章和博客条目表明 Microsoft 在 .NET 3.5 之后将不再更新它.考虑到这一点，我一直在使用实体，但发现它对于我正在使用的小型应用程序来说很麻烦且过于复杂(与 nHibernate 相同).我最近购买了 Steven Sanderson 的Pro ASP.NET MVC 2 Framework"，其中他选择使用 LINQ to SQL 作为他的 ORM，在某一点上说:

I'm trying to make an educated decision about what ORM to use for a number of legacy applications I'm responsible for porting to MVC 2. The ORMs I've looked at are LINQ to SQL, LINQ to Entities and nHibernate. L2S seemed to be the easiest, but I've found numerous articles and blog entries stating that Microsoft would no longer be updating it after .NET 3.5. With that in mind, I've been working with Entities a bit, but have found that it is cumbersome and overcomplicated for the small applications I'm working with (same with nHibernate). I recently purchased "Pro ASP.NET MVC 2 Framework" by Steven Sanderson, in which he chose to use LINQ to SQL as his ORM, at one point stating:

 I'm aware that some developers have expressed concerns that Microsoft might 
 deprecate LINQ to SQL in favor of Entity Framework. However, Microsoft included 
 and enhanced LINQ to SQL in .NET 4, so these fears cannot be entirely justified. 

我不知道他们进行了更改，也没有费心去看，因为社区的普遍看法似乎是 L2S 即将结束，将被 L2E 取代.Damien Guard 在他的博客 (http://damieng.com/blog/2009/06/01/linq-to-sql-changes-in-net-40) 给感兴趣的人.

I was unaware that they had made changes, nor had I bothered to look, as the general community opinion seemed to be that L2S was approaching end-of-life, to be replaced by L2E. Damien Guard wrote about some of the changes on his blog (http://damieng.com/blog/2009/06/01/linq-to-sql-changes-in-net-40) for those interested.

我希望有人可以阐明 Microsoft 在 LINQ to SQL 方面的立场.我正在移植和更新的应用程序有(大约)8 到 10 年的生命周期，所以我更愿意采用一种不会在那个时间范围内被放弃并且不会让我的替代品陷入困境的技术.(当然，如果有人对小商店有任何其他建议 - 我们的数据库只有不到 500 万条记录 - 我很想听听他们的意见.)

My hope is that someone can shed some light on Microsoft's position regarding LINQ to SQL. The applications I'm porting and updating have a (roughly) 8-10 year life span, so I'd prefer to adopt a technology that won't be abandoned in that time-frame and leave my replacements up creek. (Of course, if anyone has any other recommendations for small shops - our database has less than 5 million records - I'd love to hear them.)

推荐答案

我收到的信息是:期待我们真的应该尽可能多地使用实体框架；LINQ to SQL 基本上处于维护模式:它不会很快消失，但也不会显着发展.与此同时，实体框架也在不断发展，并与其他产品/框架(如 RIA 服务或 WCF 数据服务)集成.

The message I'v received is: looking forward we should really use Entity Framework in as much as possible; LINQ to SQL is basically in maintenance mode: it won't go away any time soon but it won't evolve significantly either. Meanwhile Entity Framework is evolving and also being integrated with other products/frameworks like RIA Services or WCF Data Services.

这篇关于微软是否确认了他们对 LINQ to SQL 生命周期终结的立场?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！