In “More Information on the XPathDocument/XmlDocument Change in Whidbey beta 2” Dare Obasanjo regards the
XmlDataDocument as “inefficient” and validates its existence for reasons that have more to do with Microsoft technologies (the
DataSet) than with cross-platform XML technologies. This post coupled with the Don Box classic, “Passing XML Data Inside the CLR,” reinforces the importance the
System.Xml.Xpath namespace. The types in this space should be the first choice for XML developers in .NET.
Better Late Than Never: XML Visualization in VS.NET 2003
I can’t keep up! I can’t keep up! No… I just need to focus. It would have been a great help to have the XML Visualizer for Visual Studio .NET 2003 at least a year ago… I was just reading the wrong news feeds or skimming too lightly…
Mike Brown on “issues affecting safe transport of XML over HTTP”
It’s great to read an article almost completely addressing my concerns about XML over HTTP. Importantly, Mike Brown makes reminds us to not use content type
application/x-www-form-urlencoded for XML—which is
Uche Ogbuji on XML
In “Tip: Use XML directly over HTTP for Web services (where appropriate),” Uche Ogbuji reminds us that SOAP is not for every message over HTTP. It’s refreshing to see IBM publishing this message. In an earlier post, I suggest that Microsoft is less inclined to promote such a thing.
Morbidly Curious about VML?
Back in 1998, Microsoft promoted Vector Markup Language (VML). We use it by default for Visio exports to HTML. It would be interesting to see any relationship between VML and Windows Vista technologies.
Back in November 2005, the Microsoft XML Team introduced
XslCompiledTransform. This type has quite a bit to do with the speed increases in XSL transformations in .NET 2.0.
foreach and XPathNodeIterator—Finally together
Another 2005 announcement in May by Oleg Tkachenko shows again that .NET 2.0 makes XML development fast and terse in the .NET Framework. This news should encourage us to stay in that
System.Xml.Xpath namespace as much as possible. “Finally,” there appears to be an authentically compelling and competitive reason to prefer to use .NET (or Mono) for XML-based enterprise data management solutions.