Your service generates odd WSDL? Search for Serializable attribute(blogs.microsoft.co.il)

submitted by ranwranw(263) 6 months, 15 days ago

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.

1 comment |category: |Views: 9

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by vijaystvijayst(1311) 6 months, 14 days ago 0

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.

Reply

information Login or create an account to comment on this story