Previously developers were used to deal with a single WSDL file in their WCF 3.5 services. This behaviour made it easy to share and consume the service interface.
Since WCF 4.0, Microsoft did not leave much choice and (unless some tricky workaround is applied) generates by default a WSDL with imports and references to XSD schemes and other WSDLs.
Here is a nice post that shows how to fix this issue:
Essentially it suggests to assign the same namespace to the behaviour, service and binding, and then applying custom WSDL extensions that are fortunately available in codeplex repositories.
and here:
Tags
webservice
http://laminatparquet.wordpress.com/
ReplyDeleteThis comment has been removed by the author.
Delete