How to prevent .Net SOAP Serialization from eating NewLines

Question

I'm using the built-in SOAP support in .Net through a wrapper class generated by Visual Studio from a WSDL.
Now, when I call one one of the methods on the wrapper and pass an object that contains a string with CRLF (\r\n), only the LF (\n) will end up on the server. The same happens vice-versa. When the server sends a string containing CRLF, the wrapper will only spit out the LF.

I know this is a problem that can usually be avoided by supplying an own XmlWriter to the XmlSerializer, but I can't find a place where I could specify anything like that in the provided framework.

I almost want to go with the RegEx solution provided in this thread, but I have a hard time believing that there is nothing in place to prevent this issue.

score 2 · Accepted Answer · edited May 23 '17 at 11:47

2

Just for completeness sake, I didn't find a solution that provided what I was looking for. So the best solution for my case was going with the solution proposed in this answer.

edited May 23 '17 at 11:47

Community

1
1

answered Dec 19 '11 at 23:26

Oliver Salzburg

21,652
20
93
138

score 0 · Answer 2 · edited May 23 '17 at 12:10

0

Taken from here

    XmlWriterSettings ws = new XmlWriterSettings();
    ws.NewLineHandling = NewLineHandling.Entitize;

    XmlSerializer ser = new XmlSerializer( typeof( Abc ) );
    using (XmlWriter wr = XmlWriter.Create( "abc.xml", ws ))
    {
        ser.Serialize( wr, s );
    }

edited May 23 '17 at 12:10

Community

1
1

answered Dec 22 '10 at 13:33

SwDevMan81

48,814
22
151
184

I'm aware of that solution for generic XML serialization. But in this case I am not the one doing the serialization. It happens inside the .Net Framework. So I don't see a place where I could supply custom XmlWriterSettings. – Oliver Salzburg Dec 22 '10 at 14:03

score 0 · Answer 3 · edited May 23 '17 at 12:02

Use a SoapExtension to escape the carriage returns in the stream headed to the service (SoapMessageStage.AfterSerialize).

This answer points to a good resource explaining how to implement one on v1.1 of the SOAP stuff; other examples are those which override ProcessMessage to remove invalid XML characters or log the entire SOAP conversation. (Configuration involves a SoapExtensionAttribute associating the extension with the web reference, typically setup in the web.config.)

How to prevent .Net SOAP Serialization from eating NewLines

3 Answers3