Like LINQ to XML, LINQ to XSD is a provider for querying XML data. But unlike the former, LINQ to XSD is designed to be type safe. As the name implies, it used XSD files to generate strongly typed classes.
LINQ to XSD is especially important to C# developers who currently have to sprinkle their XML code with type casts. (VB developers can side step this with Option Strict Off.) An example of this can be seen in Fabrice's weblog:
//LINQ to XML
from item in purchaseOrder.Elements("Item")
select (double)item.Element("Price") * (int)item.Element("Quantity")
//LINQ to XSD
from item in purchaseOrder.Item
select item.Price * item.Quantity
LINQ to XSD was last available for VS 2008 Beta 1, a version that was incompatible with later betas.
Community comments
XML in VB
by Stefan Wenig,
Re: XML in VB
by Stefan Wenig,
XML in VB
by Stefan Wenig,
Your message is awaiting moderation. Thank you for participating in the discussion.
It should be noted that VB already supports this (and more, like axis operators) via the import statement:
Imports <xmlns:ns="http://NewNamespace">
It's therefore not necessary to rely on option strict off when using VB9 to access schema-typed XML. My new favorite DSL for XML access ;-)</xmlns:ns="http://newnamespace">
Re: XML in VB
by Stefan Wenig,
Your message is awaiting moderation. Thank you for participating in the discussion.
Oh my, infoq is XML-aware too and "intelligently" adds closing tags...