已微软证实他们对LINQ立场SQL结束生命? [英] Has Microsoft confirmed their stance on LINQ to SQL end-of-life?

查看:106
本文介绍了已微软证实他们对LINQ立场SQL结束生命?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想对什么ORM用于一些旧的应用程序,我负责移植到MVC 2。我已经看过了奥姆斯一个受过教育的决定,是的LINQ to SQL,LINQ到实体和NHibernate 。 L2S似乎是最容易的,但我发现许多文章和博客文章指出,微软将不再是.NET 3.5后更新了。考虑到这一点,我一直与实体了一点,但发现这是我和(同与NHibernate)工作的小型应用程序繁琐,过于复杂。我最近由史蒂芬·桑德森,他在其中选择使用LINQ到SQL作为他的ORM,在一个点上,说明购买临ASP.NET MVC 2框架:

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所取代。达米安卫队写了关于一些在他的博客(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.

我希望有人能摆脱微软的关于LINQ to SQL的位置的一些情况。我移植和更新的应用程序有一个(大约)8-10年的寿命,所以我preFER采纳,将不会在该时限内放弃了技术和离开我更换了小溪。 (当然,如果任何人有小商店的任何其他建议 - 我们的数据库中有不少于5万条记录 - 我很想听听他们)

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一样Services或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立场SQL结束生命?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆