2

I have to be able to parse both these xml-s:

<!-- Case 1 -->
<root xmlns="http://www.xml.namespace/111111">
    <dataObject id="Id1" name="Name1" xmlns="http://www.xml.namespace/222222" />
</root>

<!-- Case 2 -->
<root xmlns:myNs="http://www.xml.namespace/222222">
    <myNs:dataObject myNs:id="Id1" myNs:name="Name1" />
</root>

I have to parse the <dataObject> (via XmlSerializer) into a C# model class which has this:

[XmlAttribute(AttributeName = "id", Namespace="http://www.xml.namespace/222222")]
public string Id { get; set; }

But it only works for Case 2, does not work for Case 1.
So I examined Case 1 with this code:

var xmlString = @"<dataObject id=""Id1"" name=""Name1"" xmlns=""http://www.xml.namespace/222222"" />";
var xElement = XElement.Parse(xmlString);
var idAttribute = xElement.FirstAttribute;
Console.WriteLine(idAttribute.Name.Namespace); // ""
Console.WriteLine(xElement.Name.Namespace); // "http://www.xml.namespace/222222"

Here the XElement thinks it has a namespace, while the XAttributes think they don't have any.
So the XAttributes are somehow not aware of the sibling xmlns xml namespace declaration attribute.

Is this a bug, or am I doing something wrong?

nvirth
  • 1,599
  • 1
  • 13
  • 21
  • 1
    Attributes without an explicit namespace prefix will be in no namespace. The default namespace has no effect, only on the elements. – Jeff Mercado Feb 10 '17 at 01:18

1 Answers1

0

It turnes out it is not a bug, the described behaviour fits the xml specification.

See:
XML Default namespaces for unqualified attribute names?
Applying Namespaces to Elements and Attributes

Community
  • 1
  • 1
nvirth
  • 1,599
  • 1
  • 13
  • 21