Hi,
A few days go I fiund iut that the xmlserializer strips away /r/n out during
deserialization (and just leave /n)
... I found out that you can resolve this problem using the deserialize
overlaod that takes an xmltextreader instead of a stream ..
However when it's time to Web Services you have no such a control over the
deserialization phase AND I found out that WS strips out /r/n (an leave /n)
... I understand there are some XMl specs related to this .. however . what
one should do to have a /r/n sequence into a string property of his own
custom object ?
I saw that writing /r/n as unicode numbers does work .. however this implies
writing some custom soap extension / http module to replace 0d,0a sequences
to their unicode equivalence ( ..and .. btw .. how do I avoid to mix up
binary data eventually transmitted that contains this sequence ?) .. are
there better way to solve this ?
Any suggestion is appreciated.
thank a lot
Enrico Sabbadin