What's New in the XLinq CTP?

re: What's New in the XLinq CTP?

Jerod Moemeka — Sun, 21 May 2006 07:32:21 GMT

Can you explain the rationale behind excluding the xml literals from c#

re: What's New in the XLinq CTP?

XmlTeam — Mon, 22 May 2006 07:38:58 GMT

XML literals implies that the host language essentially becomes a superset of XML. That's a pretty big change to C#, whose user base has somewhat different expectations than the VB customer base. For example, an XML MVP http://donxml.com/allthingstechie/archive/2006/02/03/2517.aspx believes that XML literals are OK for VB user scenarios but hopes that C# doesn't support them.

See the "official" answer in http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=397079&SiteID=1
"The C# design team has prioritized language changes like XML literals down quite a bit, believing that the XLinq constructors offer an equivalent degree of functionality."

So, it depends on how the different approaches in VB and C# are received by the customers once Orcas ships. If there is a lot of update of the VB feature, it might well find its way into the next release of C# after Orcas ... or maybe C# users will let us know that they are happy with functional constructors and the "paste XML as XElement" feature in the IDE.

re: What's New in the XLinq CTP?

Jerod Moemeka — Mon, 22 May 2006 19:00:09 GMT

If your deadlines don't allow you to that's fine, if Microsoft wants VB to have a cool feature C# doesn't have that's fine too. I; however, don't buy the 'its not a good idea' line. I thought the overall idea behind C# was to create a modern tool that converged the three predominant technologies in a seamless way ?!? The Paste as XML option is NOT a compromise because it looks NOTHING like xml. It would be no different than giving a 'paste as sql' tool rather than the LINQ constructs.

re: What's New in the XLinq CTP?

mikechampion — Tue, 23 May 2006 00:47:38 GMT

It's not a matter of deadlines so much as a matter of making absolutely sure that this is the right thing. It may be a good idea, we get as many people asking us NOT to do it as we do getting people asking for it.

It's true that that Paste as XElement produces something that doesn't look like XML, but then again it doesn't have to invent a syntax for expresion holes -- paste in the XML text to generate the constructors, then modify them to populate the XML from whatever logic or lookups is necessary for your app.

But thanks for letting us know how you feel about this. It will be seriously considered the next time around.

Non-merging text nodes in XLinq: They're Baacckk!!

mikechampion's weblog — Fri, 02 Jun 2006 18:45:57 GMT

When I described the changes to XLinq in the May CTP, I said:
Note that whereas DOM explicitly allows...

re: What's New in the XLinq CTP?

forced sex — Wed, 07 Jun 2006 01:36:20 GMT

Wellcome to the real world.

On XSLT and LINQ to XML...

Alex Barnett blog — Fri, 23 Jun 2006 19:28:23 GMT

Yesterday Mike Champion (on XML team in Data Programmability) wrote up a post answering the question:...

Erik Meijer on LINQ, XML, and the future at XTech 2007

Microsoft XML Team's WebLog — Fri, 18 May 2007 07:12:00 GMT

Erik Meijer gave a talk at the XTech 2007 conference on LINQ, XML, and his vision for "LINQ 2.0 ". The

Scott Hanselman's Computer Zen - Paste XML as XLinq XElement Visual Studio AddIn

Scott Hanselman's Computer Zen - Paste XML as XLinq XElement Visual Studio AddIn — Tue, 28 Aug 2007 21:20:23 GMT

PingBack from http://www.hanselman.com/blog/PasteXMLAsXLinqXElementVisualStudioAddIn.aspx

Microsoft XML Team s WebLog What s New in the XLinq CTP | fix my credit

Microsoft XML Team s WebLog What s New in the XLinq CTP | fix my credit — Wed, 17 Jun 2009 04:54:37 GMT

PingBack from http://fixmycrediteasily.info/story.php?id=18170