Wcf – Where is wsdl file in WCF service

wcfweb serviceswsdl

I have created a WCF web service and locally when I access the wsdl file like (http://localhost/myservice/service.svc?wsdl it shows the wsdl file just fine. I then uploaded it to my virtual server hosted by GoDaddy and when I call http://my ip address:myport/service.svc?wsdl the result is the page where it states "You have created a service". This is the same page that displays when I call the same url but without the ?wsdl (http://my ip address:myport/service.svc). How can I get at my wsdl file on the virtual server? Why did this happen differently than my local machine?

Best Answer

Make sure that your config file in hosting environment allows retrieving the WSDL document. It should contain this:

<behaviors>
  <serviceBehaviors>
    <behavior name="metadata">
      <serviceMetadata httpGetEnabled="true" />
    </behavior>
  </serviceBehaviors>
</behaviors>

And reference this behavior in your service configuration.

Edit:

Just to make it clear. With default WCF behavior, the WSDL file is nowhere. It is auto-generated and this auto-generation must be allowed.

Related Solutions

.net – WCF service startup error “This collection already contains an address with scheme http”

In .Net 4, you can use the multipleSiteBindingsEnabled option:

<system.serviceModel>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true">
    </serviceHostingEnvironment>
</system.serviceModel>

Then, you won't have to specify each address.

http://msdn.microsoft.com/en-us/library/system.servicemodel.servicehostingenvironment.multiplesitebindingsenabled.aspx

Wcf Extract wsdl from WCF Service with Flattened WSDL

Yes, you should still be able to use svcutil to extract the WSDL from your service, even if you have an extension installed that will flatten the WSDL.

To download the metadata document(s) from your running service, use this command:

svcutil /t:metadata http://service/metadataEndpoint

You need to point your URL to the metadata endpoint defined in your config, e.g. the endpoint that's defined to use "mexHttpBinding" or "mexTcpBinding" and the "IMetadataExchange" contract.

If you don't have any metadata exchange endpoints defined, you won't be able to retrieve that information, obviously.

Best Answer

Related Solutions

.net – WCF service startup error “This collection already contains an address with scheme http”

Wcf Extract wsdl from WCF Service with Flattened WSDL

Related Topic