« LINQ Part 2 - Filtering Sorting Using Data from the Database | Main | LINQ Part 4 - What's behind a query expression? »

03/17/2006

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

vinnie

awesome series, thanks. seeing LINQ in action helps me understand and appreciate the new C# 2.0 features. btw... i think u mean XLINQ up there in your example, not XQuery :)

Christian Nagel

Vinnie, thanks for your comments :-) Of course I meant XLINQ. Corrected.

Keith J. Farmer

One of the things I've disliked about the preview of XLinq is the explicit casting that is constantly being done upon accessing XElement and the like. I think it would be a good exercise to implement and demonstrate a typed XDocument that implements a schema. It shouldn't be difficult...

Christian Nagel

Keith, in a future entry of this series I will show typed XML. This is supported by VB9. I hope for C# 3.0, too.

Jay R. Wren

since LINQ exposes the expression tree, it SHOULD be possible to actually write something to read this expression tree and output XSLT! So you could write LINQ, and output equivalent XSLT.

The comments to this entry are closed.


IMPORTANT: This is archived - and quite likely outdated - content, only kept online for reference purposes

Please visit thinktecture.com for up-to-date technical content.