Is LINQ to SQL deprecated?

For all the "Linq-to-SQL is dead" folks: Scott Guthrie himself clearly mentioned at TechEd Europe that Linq-to-SQL is FULLY SUPPORTED in . NET 4, and Damien Guard posted a blog post on what changes and improvements have been made for Linq-to-SQL in . NET 4 To quote Mark Twain: "Reports of my death have been greatly exaggerated.

For all the "Linq-to-SQL is dead" folks: Scott Guthrie himself clearly mentioned at TechEd Europe that Linq-to-SQL is FULLY SUPPORTED in . NET 4, and Damien Guard posted a blog post on what changes and improvements have been made for Linq-to-SQL in . NET 4.To quote Mark Twain: "Reports of my death have been greatly exaggerated"......

6 Add to that what Hejlsberg said in a Redmond Dev News interview: "LINQ to SQL is not dead. I can assure you, it is not dead. Nothing ever goes away.

We have never done that and we never will. " reddevnews. Com/blogs/desmond-file/2008/12/… – KristoferA - URL1 Jun 15 '10 at 0:51 While it is not dead or dying, it is deprecated.

That is the main question. There are articles from Microsoft saying the move is to push their flagship ORM - EF. L2S is Fully Supported, and critical for everyone to know / learn... however the focus on it has indeed changed, similar to the silverlight / html5 and mvc / webforms .. None of the previous technologies are "dead" just not moving forward at the same pace or direction as other things.

Deprecated might be a little strong of a word as that would insinuate that it will eventually not be supported, or strongly disapproved of. – Tom Stickel Jul 27 at 19:00 what Hejlsberg said is an innately false statement things change and they do go away or windows 3.1 would still be in support . Net 1.1 would be officially supported on server 2008 and microsoft would still be supporting the iron languages and like tom said dead!

= deprecated it is still in use and supported however it is no longer being actively developed I would advise keeping your support for linq to sql active but begin moving forward into entity frame work for current and future development – Chris McGrath Aug 18 at 6:03.

No it is not. The team are still working on improving it.

Last I checked, this very site uses (or used to use) Linq To SQL. Joel Spolsky mentions this in his GoogleTechTalk: youtube.com/watch?v=NWHfY_lvKIQ. When speaking of software, "dead" is a figurative modifier (software doesn't die in any literal, biological sense), so this debate can linger on as long as the involved parties refuse to define in any literal sense what it means for "Linq To Die".

Or, LTD for short. Hence, as of this moment, the LTD debate has lingered for two years. All because of a little linguistic ambiguity.

Those who say that "L2S is dead" are generally referring to the fact that L2S isn't going to receive too many (if any) new features. Updates to Linq (like the updates mentioned in Damien Guard's post) are likely to be confined to performance, usability, and stability updates. Of course, some developers might actually argue that this is a good thing (probably the same developers who are a wee bit angry about the new dynamic type).

Those who say that "L2S is not dead" are generally referring to the fact that L2S isn't going to be cut altogether from . Net (at least not anytime soon). Think: URL2 may lose some of its traction amongst practicing developers (and that may be the unspoken desire of those crafty folks at Microsoft), but that doesn't mean that you won't be able to use L2S if you want to.

It just means that Microsoft isn't trying to tantalize the masses with it. When starting a project, I actually think it's great that I have a choice between EF and L2S.As Bill Wagner points out, there's a time and a place for both.

Let's ask google. "Is linq to sql ..." worth using : 167,000 hits dead : 136,000 hits going away : 28,300 hits deprecated : 15,100 hits good : 2,980,000 hits in . Net 4 : 1,980,000 hits.

Make sure to have a look at this article posted on InfoQ. Com - it's a really interesting one. Its conclusion: "Over the long run LINQ to SQL and LINQ to Entities will merge.In the mean time, development work on LINQ to SQL will not end entirely.

I guess it's inevitsble that they'll merge. EF is really an enterprise level implementation of LINQ over db objects. Linq2sql was to all intents a proof of concept(and a lot more) that actually grew legs but fuelled many of the ideas that we now see in EF.At the end of the day, the DAL layer (nhibernate, EF, l2s, subsonic etc) should be pretty far down the chain so as to negate any differences in the client BO code that implents the LINQ service - hot swappable would be the end game via DI.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.