Linked by Thom Holwerda on Mon 19th Nov 2007 21:16 UTC, submitted by Wyatt Lyon Preul
.NET (dotGNU too) Scott Guthrie has announced that Visual Studio 2008 and .NET 3.5 are now available for download and provides a tour of some of the new features. "Visual Studio 2008 and .NET 3.5 contain a ton of new functionality and improvements. Below are links to blog posts I've done myself as well as links to videos you can watch to learn more about it."
Thread beginning with comment 285661
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Ruby on Rails
by MollyC on Wed 21st Nov 2007 01:09 UTC in reply to "RE[4]: Ruby on Rails"
MollyC
Member since:
2006-07-04

Agreed.

And besides "LING to SQL" and "LINQ to XML", Microsoft has also created LINQ to Objects, which gives LINQ the ability to query any collection or object that implements IEnumerable. And there are already third party LINQ providers specializing in querying particular data (web queries, RSS feeds, etc).

And of course, there's PLINQ (Parallel LINQ) that automatically runs queries on multiple cores/cpus.
http://msdn.microsoft.com/msdnmag/issues/07/10/PLINQ/default.aspx

LINQ rocks. ;)

Reply Parent Score: 2

RE[6]: Ruby on Rails
by StaubSaugerNZ on Wed 21st Nov 2007 18:58 in reply to "RE[5]: Ruby on Rails"
StaubSaugerNZ Member since:
2007-07-13

May I ask the question as to whether LINQ has a syntax that is the same across all database back-ends or is it specific to the database in question? If it is specific to a particular database then that sux from a migration point of view (which happens in the real world). I've just completed a government Postgresql to Oracle project and the database specific SQL in JDBC sux. They should have used Hibernate which has the same syntax no matter what the target is.

Reply Parent Score: 1

RE[7]: Ruby on Rails
by smitty on Thu 22nd Nov 2007 08:09 in reply to "RE[6]: Ruby on Rails"
smitty Member since:
2005-10-13

LINQ is actually built into the C# (and other .NET) languages, so it is necessarily the same for all backends. However, you do have the option of sticking in custom stuff yourself into the code generated by the backends. So by default it is the same everywhere, but customizable enough that you can make it non-portable.

Reply Parent Score: 2