cjard
Well-known member
- Joined
- Apr 25, 2006
- Messages
- 7,081
- Programming Experience
- 10+
Guys
I have some code that the xmlserializer is deserializing to.
the xml looks like:
A certain property looks like:
When XmlSerilaizer deserializes the object, the abc property is null.
If I remove the Unqualified:
It works fine
XSD.exe was used to go from XSD to .vb, and it put the parameter for Form in there.. I'm curious to know, if we explicitly state Unqualified, then why does my unqualified tag not deserialize, but if we leave it at (Default) then it deser's fine?
I have some code that the xmlserializer is deserializing to.
the xml looks like:
VB.NET:
<request xmlns="namespace">
<abc attr="val"/>
</request>
A certain property looks like:
VB.NET:
<System.Xml.Serialization.XmlElementAttribute("svaRef", Form = Unqualified)>_
Public Property abc As requestAbc
When XmlSerilaizer deserializes the object, the abc property is null.
If I remove the Unqualified:
VB.NET:
<System.Xml.Serialization.XmlElementAttribute("svaRef")>_
Public Property abc As requestAbc
It works fine
XSD.exe was used to go from XSD to .vb, and it put the parameter for Form in there.. I'm curious to know, if we explicitly state Unqualified, then why does my unqualified tag not deserialize, but if we leave it at (Default) then it deser's fine?