You can always implement IXmlSerializable and do whatever you fancy through XmlReader.
Right, I did not consider such path. This would definitely solve my problem, although I was hoping for some cheaper solution :) Thanks! – Piotr Owsiak Jul 22 '09 at 15:42 BTW, you don't need Serializable for XML serialization.
XmlElemenht("Name") can be omitted too, since in this particular case it does not change XMLSerializer's default behaviour. – Anton Tykhyy Jul 22 '09 at 17:33.
So, even though the element actually contains XML elements, you want . NET to pretend it is really a string? I don't think this is possible through standard serialization.
However, you could load the XML, transform the PersonXml and properly escape it and then replace the contents of the PersonXml with the newly escaped data. It would involve manually manipulating the XML before deserializing it, but then you could keep the XML elements under the PersonXml.
Yeah, but this seems to me like too much hassle and a pretty ugly solution :) – Piotr Owsiak Jul 22 '09 at 15:36.
Just use XmlElement for PersonXml. It's always a bad idea to pretend that XML is the same thing as String.
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.