Microsoft is going to ship LINQ next year. This statement is as sound as ‘US Army is not going to leave Iraq in the next 10 years”.
With LINQ they added a very power data sub-language to the two pet languages of theirs, C# and VB.Net. VC should not complain. They have their own problems to fry with things like re-implementing the code model for VS 10, improving the performance for common usages, expose C++ grammar’s AST programmatically and the miscellaneous. They got Class Designer included in VS 2008 Beta 2 with its own set of problems because System.Windows.Documents.FixedDocument cannot handle extremely wide XPS documents.
But I haven’t discussed one child of Microsoft’s parentage which will need LINQ support and that is ‘PowerShell’. Powershell has the capability to embed C# code (and if I am very much wrong, only C#) as its script which allows it to do almost anything a regular program can do. This means, when out-of-box commandlets are insufficient you can go straight for C# as your first choice and resort to more esoteric means if need by.
But surely, if you can do anything with C# in it, you should be able to mix-in a little of LINQ too. SilverLight 1.1 will have LINQ support,
But I haven’t heard any news about LINQ support in PowerShell.
So why leave this particular kid alone?
P.S. I thought I should note that some of the links point to bugs I have filed on connect.