[Mono-list] Re: XmlSerializer.cs
Ajay kumar Dwivedi
Wed, 8 Jan 2003 21:22:16 -0800 (PST)
I was the one who worked initially on the XmlSerializer. I had made it work
for most of the things I required (for schema serialization).
Then I switched from the programming world and did not get time to finish
it up. I remember one of the reasons I did not implement Arrays was that how
they are serialized was not clear to me and another that it was not urgent for
me at that time. Moreover you would find things like sorting algoritm that
would make no sense to anybody why they are there. Some of the "features" were
added to be compatible with the MS output for compariasion etc.
Another thing to note in the serializer is that there were a lot of other
"useless" classes like XmlSerializtionWriter that were not used by me since
there was no documentation available on them and the way they could be used.
Maybe they have been incorporated into XmlSerializer now.
Let me take a look at the XmlSerializer this weekend and then I can either
complete it or provide you some ideas on how it works.
If you could send me some sample you are trying to serialize with arrays,
maybe we can work together on it.
--- firstname.lastname@example.org wrote:
> 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
> 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
> > 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
> > email@example.com
> > www.codenoevil.com
> > Code Made Fresh Daily™
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.