Your service generates odd WSDL? Search for Serializable attribute

[ERR!]
added by ranw
11/11/2011 9:27:16 PM

172 Views

A problem I’ve encountered at a customer I work for was very strange behavior regarding the WSDL being generated by it’s service. The WSDL didn’t contain any class property, moreover it did contain private members of a class being exposed by the service.

Read the full story
C#
1 comments
vijayst
11/11/2011 9:28:34 PM
I encountered this problem in one of the projects where I was re-exposing the WSDL of another service. I used wsdl.exe to generate the proxies. I used the option to generate only public fields. This resolved the problem for me.

Later, I realized that I need to use XmlSerialer for SOAP calls. By using the XmlSerializer, I could use public properties also.

Thanks for the submission.