 |
|
|
I have read that MSXML 4-6 only support XPath 1.0 which does not support
default namespaces.
We have a legacy application in cpp (unmanaged, several actually) that needs
to interoperate with .net, since we are trying to migrate to .net when and
where we can. But I keep running into system level software that do not
support the same levels of specifications, in this case, xpath.
In this particular application there is a class that is serialized with the
DataContractSerializer and then reloaded in the cpp application. Sounds good
but, the xml is created using a default namespace that will load in MSXML
6.0 but you can not do a selectNodes or selectSingleNode.
I would have thought that someone would have considered this when
implementing the xml parsers. It looks like the .net group goes on totally
independant of the rest of the world, or the native guys just don't bother
to keep up.
Is there a way to serialize the class in .net so it can be utilized in cpp
with MSXML 6.0 and not destroy the wcf functionality?
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
