Talk:Language Integrated Query

From Wikipedia, the free encyclopedia

Having used LINQ in a project for the past 2 weeks, I am amazed at the power it gives developers. Instead of having to mix my code with SQL, I can treat the database tables as if they were classes. The current release of LINQ still lacks intellisense but it had enough added value to move my project into it. Performance is also impressive.

--Ohadgliksman 13:13, 24 April 2006 (UTC)

[edit] Haskell influence

You guys might want to add some historical detail in; from pg 6 of "The History of Haskell":

But many of the features in C# were pioneered by Haskell and other functional languages, notably polymorphic types and LINQ (Language Integrated Query). Erik Meijer, a principal designer of LINQ, says that LINQ is directly inspired by the monad comprehension in Haskell.

--maru (talk) contribs 02:25, 15 July 2006 (UTC)

Those features werent there in imperative languages, and c# is not a functional language (like haskell, lisp) but an imperative one (like c, c++, java) --soum^সৌমোyasch 06:15, 15 July 2006 (UTC)

[edit] Release date

I am confused why you have deleted my paragraph Soumyasch. It was there to explain the apparent pushing back in release from .NET 3.0 to 3.x (ie it won't be in the Vista release cycle, yet this has been promised for 12 months). But your reason for deleting was simply 'not in 3.0' !! Please explain.

In the mean time, I have replaced the section with one not explicitly mentioning a previously planned release in 3.0 - I feel it is important people know this tool won't be available in the Vista cycle, as was previously the impression.

80.177.152.35 09:04, 13 August 2006 (UTC)

I deleted it bcoz it was never supposed to be released with .NET 3.0 (which is WinFX, still CLR 3.0), it was (and still is) to release with C# 3.0, and the version of CLR (presumably 3.0) accompanying it. The previous version gave an impression otherwise. --soum^সৌমোyasch 09:23, 13 August 2006 (UTC)

Ok, how about fixing it next time instead of hitting the Delete key ;) BTW Linq still produces 2.0 IL.

Incidentally, if Orcas is released sometime after Vista, what do we use to develop WPF / WCF apps in, during that period? Some expansion pack for VS2005?? (not CTP's obviously, since they're not of production quality). 80.177.152.35 14:23, 13 August 2006 (UTC)

Linq doesn't produce IL 2.0, Linq preview does. Who knows whether the release version will make use of IL additions or not! And WPF/WCF are essentially additions to FCL, so VS 2k5 is enough. Maybe add-in packages will make the IDE WinFX aware, meanwhile.

And as far as deleting goes, ur lines were from the assumption Linq was supposed to be in .NET Fx 3.0, so nuking it seemed best, so that revision of the statement wont be born from the misconception.--soum^সৌমোyasch 16:05, 13 August 2006 (UTC)

You might find this interesting http://msdn.microsoft.com/chats/transcripts/vstudio/05_1020_csharplinq.aspx , specifically "C# 3.0 will work on .NET Framework 2.0" (daigoh, QA at Microsoft). Also, when someone asks if it's appropriate to ask about .NET 3.0 enhancements in a 'C# 3.0 / Linq' chat, Jomo replies "I think 3.0 questions are appropriate". No ambiguity about that, he's talking about .NET 3.0, suggesting strongly the two are tightly connected (at least when this chat took place)

Also http://msdn.microsoft.com/chats/transcripts/vstudio/05_0922_csharp.aspx does not make a distinction between C# 3.0 and .NET 3.0, again the two are referred to as if they were part of a single release cycle (Vista).

The situation has changed now, obviously. But then, that was the point of my original post! I'm providing lots of references. Can you provide some to show .NET 3.0 has *always* been planned for release before / seperately from C# 3.0?? 80.177.152.35 17:54, 13 August 2006 (UTC)

The confusion stems from the fact that the current ".NET 3.0" release previously (for example in September 2005) was not assigned a special .NET version number, but instead was called "WinFX". At that time (and this is the time the chat transcript you linked stems from), ".NET 3.0" was used to (informally) denote the next platform upgrade (including C# 3.0, LINQ, and maybe even a new CLR 3.0), whereas "WinFX" was a set of libraries (originally for Vista only).

In the meantime, it was decided that WinFX should go into the main .NET libary. This library update is now called ".NET 3.0" and does not contain a change of the underlying platform or the standard compilers. What was once informally called ".NET 3.0" (i.e. C# 3.0, LINQ, etc) is now usually referred to as "Orcas" (which is the name of the next VS version), some also call it ".NET 3.5". See also Microsoft_.NET_Framework.

I think it was never intended that LINQ should ship together with WinFX, it's just the assignment of a whole .NET version number to WinFX which leads to this confusion. 128.130.173.30 10:55, 27 November 2006 (UTC)