Where does the serialization happen?

I’m trying to find the code that performs the SOAP serialization when we call a ClientBase<T> method of a SvcUtil generated proxy. Which file(s) carry that code?

I have tried to generate the same SOAP envelope that the proxy creates by serializing the SvcUtil generated request classes using DataContractSerializer, XmlSerializer and SoapFormatter (3rd party NuGet package). However, none of them produce the correct SOAP request. So, I’m interested in seeing the code that produces the correct SOAP xml.

[darthkurak]

Any update here? I am facing same issue. Can’t find a generic way to serialize/deserialize wcf generated classes 😦

[sameera]

@sameera, if the problem is having so many operations and taking a large amount of memory for the ChannelFactory/large amount of time to create, you can split up your contract into multiple interfaces. That way any one ChannelFactory isn’t too big. That you you only pay the cost of the operations you need.

At operations level, there’s only a handful. However, each operation can work with a large number of types and probably, its the number of these record types that causing the problem. To give more context, this is the Reference.cs generated by ServiceUtil. https://github.com/sameera/lib-netsuite-servicemgr/blob/master/Celigo.SuiteTalk/src/Connected Services/SuiteTalk/Reference.cs

So, I believe splitting up the client in to multiple operations wouldn’t help.

I also had a look at your other issue to get more context. If you use ChannelFactory.CreateChannel(Uri uri), you can have a single channel factory which works against multiple endpoints.

This is only if all endpoints belong to the same domain, isn’t it? In our case, webservice for each customer is accessible through a domain specific to the customer.

If you are using XmlSerializer, you can pre-generate the serializer to reduce startup time.

We’ve done this and it reduced the time by 1-2 seconds. Unfortunately, that’s only about a 10-15% improvement.