[Mono-list] Re: XmlSerializer.cs

[tim@timcoleman.com]

Hmm...

I seem to remember working on that class quite a while ago (like in
the summer/early autumn).  I don't think I've really touched it since
I left web services behind to work on System.Data.  And I haven't 
actually worked on System.Data in about a month due to work and 
holidays.

My point is that I can't quite remember how all of the serializer
stuff worked.  I do know that I was trying to move a lot of things
around up until the point where it became unmanageable.  I know there
are a lot of things that need to be done in there.  Hopefully one
of the other people that worked on it will be able to offer you some
assistance.

Cheers,

Tim

> I'm currently doing development work inside XmlSerializer.cs.  My 
> original intentions were to develop Deserialize(), but my example I was 
> using an Array so I stumbled on the fact that SerializeArray() wasn't 
> implemented yet.
> 
> As you can imagine, this opened up a can of worms.  I need someone to 
> help me gain a much better understanding of the typeTable.  Arrays, as 
> you know, have two extra Attributes associated with them, 
> XmlArrayAttribute and XmlArrayItemAttribute and they somehow disappear 
> from the member when it gets to the SerializeArray() method.
> 
> I notice that more generic XmlAttributes are stripped from the members 
> when they are added to the typeTable.  There's a FillArrayType() method, 
> but there is no intuitive place to cache these additional values.  I do 
> not want to start create more and more objects for restoring information 
> that we already have.
> 
> Would whome ever spent the most time on this help me out with this?
> 
> -- 
> David B. Bitton
> david@codenoevil.com
> www.codenoevil.com
> 
> Code Made Fresh Daily™