IXmlSerializable seems pretty similar (albeit XmlWriter XmlReader oriented). I'm also not sure why deserialize would return something; shouldn't we be deserializing into the current object?(else it is an IXmlConverter.
IXmlSerializable seems pretty similar (albeit XmlWriter/XmlReader oriented). I'm also not sure why deserialize would return something; shouldn't we be deserializing into the current object?(else it is an IXmlConverter, if you see what I mean). Re the tags... the question is unclear; you don't show any tag names in either code or string constants... But it is a lot easier to just use XmlSerializer and let it worry about everything... XmlType("foo") public class Foo { XmlAttribute("bar") public string Bar {get;set;} XmlElement("baz") public int Baz {get;set;} }.
Precisely. I suspect the OP wasn't aware of the functionality built into the BCL, so this is good advice. – Noldorin Jun 3 '09 at 12:13 What is BCL, by the way?
– chester89 Jun 3 '09 at 12:17 1 Base Class Library - i.e. The classes that are supplied in the . NET framework – Marc Gravell?
Jun 3 '09 at 12:18 I`ll be working with LINQ and I didn`t plan to use XMLWriter and XMLReader – chester89 Jun 3 '09 at 12:26 If you use XmlSerializer you don't have to use XmlReader/XmlWriter directly - that is largely the point. Re the question; you could perhaps use the same attributes to underpin your own custom serializer? – Marc Gravell?
Jun 3 '09 at 12:46.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.