I've been caught up in a bunch of other activites since my last post and did not think I will have to wait this long before making my next post... well...
So I'll be continuing from where I stopped last time...
Coming in at Number 9 is XML Standards Support by Default. As mentioned in the previous post none of the readers will have DTD support and as such we will not be able to resolve entity references however just like the full Desktop Framework you will be able to set the ConformanceLevel of the XmlReader as demonstrated in the code snippet. Pretty much everything covered in this feature also applies on NETCF with the exception of DTD support.
The Number 8 feature is Universal Type Support and Conversion. Yes in NETCF V2.0 the XmlReader and XmlWriter classes have also become type aware. In the upcoming Beta1 release we do not have the XPathNavigator class (it is a feature we are considering for V2.0 but it’s not going to be in Beta1). Just as Mark explained you will be able to use the ReadValueAsXXX methods on the XmlReader class to read and convert a CLR value in a single method call, you will also be able to use the WriteValue methods to write CLR values.
The Number 7 feature is XmlReader and XmlWriter Usability. I will not repeat all that he mentioned. I think it will be sufficient to state that all the new helper methods are fully supported on NETCF with the exception of the WriteNode method (this is dependent on the availability of the XPathNavigator in V2.0).
The Number 6 feature is The XQuery Language and the answer to this is a polite No. We do not plan to make this available in V2.0 of NETCF. I’m sure you already know that System.Xml in V2.0 of NETCF comes with XPath 1.0 support exposed via the SelectNodes and SelectSingleNode methods of the XmlNode class.
The Number 5 feature is Security.
Mark discusses the use of the Evidence property of the XmlReader – this is not available on NETCF Beta1. The ProhibitDtd property is also not supported on the XmlReaderSettings class because we always throws an exception whenever any DTD is encountered in the XML.
I plan to discuss the remaining 4 features in my next post.
As always feedback and comments are most welcome.