A few weeks ago, some debate sparked regarding the IBlogThis (now IBlogExtension)
interface, and, at that time, Don suggested using
IXPathNavigable or XPathNavigator over XmlDocument through the interface. And so,
we now have an IBlogExtension interface that uses IXPathNavigable indeed.

However, this raises a small question: Why would you prefer IXPathNavigable
over XPathNavigator directly? After all, the former has only one method (CreateNavigator())
so you can pretty much only use it to get an XPathNavigator instance anyway.

While on the topic, I figure this could be a good time to make a few
wishes regarding the Xml support in the .NET framework: Bridge the different
abstractions you guys provide! Overall, I really like the XML support in the framework
(especially compared to what we used to have before), but sometimes, you find significant
gaps in how the different abstractions provided interact. So yes, I'd like things
like an XPathNavigatorReader and
to be provided by the framework. Is that too much to ask? I think not.


Tomas Restrepo

Software developer located in Colombia. Sr. PFE at Microsoft.