[Mono-devel-list] Re: XmlSerializer status

[ginga at kit.hi-ho.ne.jp]

Hello,

> > * When I tried to serialize XmlQualifiedName as nullable element
> >   (IsNullable=true), MS.NET (my environment is 1.0) reports an
> >   error that it cannot be nullable. I think, it is because
> >   XmlSerializer should ignore XmlQualifiedName.Empty (and those
> >   which equals to Empty), and to do so, IsNullable is in the way.
> >   It also prevents me from deserializing my simple xml schema stuff
> >   (emptiable XmlSchemaElement.RefName).
> 
> I haven´t tested this. Is it serialized as an attribute?

Oh, sorry I missed to write, and I found it is not serialization 
reader in fact that prevents me. Yes, it is about attribute that
"should be ignored". As to element serialization, its output is 
<qname xmlns="" />. I attached what I tried.

> Ok, fixed, thanks!. I´ve modified your patch a bit. I now deal with the
> special
> case of QNames in the GetValueFromXmlString method.

That place is better :)

> > With your recent fix, I think it won't be so long to become
> > able to deserialize XmlSchema. (it is really nice example,
> > rich in XmlAttributes. ServiceDescription class is also.)
> Nice nice, it will be also a good test case.

Yes, but before using it practically, we have to consider
serialization order problem lying, as Erik has been mentioned.
I assume that the problem might be solved with use of LayoutKind
(StructLayoutAttribute), but as to extended (derived) classes, 
I have no idea yet.

  Atsushi Eno
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qname.cs
Type: application/octet-stream
Size: 606 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20030614/9994f25f/attachment.obj