Type safety - LINQ to DataSets Part 2

re: Type safety - LINQ to DataSets Part 2

Eisenberg — Tue, 06 Feb 2007 20:38:59 GMT

Why even bother with datasets? I was hoping that MS was going to wise up and mark this functionality as Deprecated or Obsolete in the next version of ADO.NET. (Isn't the Entity Framework supposed to replace DataSets?) Every scenario I have examined that uses datasets has had major issues and generally horrid software design. They are the most embarassing and backwards part of .NET.

re: Type safety - LINQ to DataSets Part 2

Beth — Wed, 07 Feb 2007 01:59:28 GMT

I'm really looking forward to your VB.NET sample.

re: Type safety - LINQ to DataSets Part 2

Erick Thompson — Fri, 09 Feb 2007 17:45:54 GMT

Hi Eisenberg,

Thank you for taking the time to read our blog. The DataSet is actually a widely used component, and is quite good at what it was designed to do. While there may be some horrid software designs out there that use it, I think that could be said for a lot of other technologies as well. For an in-memory relational data cache, the DataSet is highly effective, and thus it makes perfect sense to enhance it with LINQ.

Interesting Orcas & LINQ Links

John Papa [MVP C#] — Fri, 09 Feb 2007 18:55:56 GMT

Here are a few good links to Orcas material (some old and some new). There is a lot of good and bad material

New and Notable 139

Sam Gentile — Mon, 12 Feb 2007 01:00:45 GMT

Winter has finally set in with single digit temps and minus degrees wind chills but still no snow. WPF/Avalon

Querying DataSets – Introduction to LINQ to DataSet

ADO.NET team blog — Thu, 15 Feb 2007 23:51:29 GMT

Greetings fellow data junkies! My name is Erick Thompson, a PM at Microsoft who is working on driving

re: Type safety - LINQ to DataSets Part 2

daoud — Wed, 25 Jul 2007 12:24:16 GMT

what is the vb.net equvelent for that code ?

re: Type safety - LINQ to DataSets Part 2

Jerin — Mon, 13 Aug 2007 14:41:08 GMT

Will i be able to work with LINQ in my visual c# express edition 2005 version?

When i tried to include using System.Linq name space and tried to run the application it showed an error

Error 1 The type or namespace name 'Linq' does not exist in the namespace 'System' (are you missing an assembly reference?)

Can you please help me out??

re: Type safety - LINQ to DataSets Part 2

Nick — Sat, 22 Sep 2007 03:16:37 GMT

I'm getting the same error:

The type or namespace name 'Linq' does not exist in the namespace 'System' (are you missing an assembly reference?)

and cant figure out what reference I need to make. When I go to the website property pages / references and click "Add" I do not see a System.Linq to add as a reference.

Anyone have any ideas...?

re: Type safety - LINQ to DataSets Part 2

Nick — Sat, 22 Sep 2007 03:24:01 GMT

I figured it out... A reference to System.Core is needed in the progect...

re: Type safety - LINQ to DataSets Part 2

Paul — Tue, 15 Jan 2008 13:39:03 GMT

Thanks Nick. I got to solve the problem through your post.

re: Type safety - LINQ to DataSets Part 2

Pramod — Mon, 21 Jul 2008 08:54:42 GMT

Compare two large data tables A and B using linq and get the records which exist in dataTable A but does not exist in B

re: Type safety - LINQ to DataSets Part 2

Baraka — Sat, 25 Oct 2008 17:28:37 GMT

I am new to the whole LINQ thing but I can see already that it is great technology. However, it is a shame that such great technology is handicapped by the fact it cannot create DataViews that are not limited by certain LINQ operators such as GROUP BY.

It has been a long time since it was introduced, by any chance has MS been able to make the LinqDataView free of its limitations? I certainly wish to use LINQ but its DataView limitations are putting me off.