This project has moved and is read-only. For the latest updates, please go here.

location attribute doesn't seem to be working


We have the f5 environment situation and were already using the single wsdl solution, I need to use the location attribute so that I can display the wsdl location with https:// Setting the location in development or in integration does not change the url. I've read the instructions for this and can't see what I'm doing wrong, here are my config settings:
        <add name="wsdlExtensions" type="WCFExtrasPlus.Wsdl.WsdlExtensionsConfig, WCFExtrasPlus, Version=, Culture=neutral, PublicKeyToken=f8633fc5451b43fc" />
        <binding name="BasicUnsecured" maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" maxBufferSize="2147483647">
          <security mode="None"></security>
          <readerQuotas maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxDepth="32" maxNameTableCharCount="2147483647" maxStringContentLength="2147483647" />
<behavior name="BasicBehavior">
          <serviceMetadata httpGetEnabled="True" />
        <behavior name="endpointBehaviorPing">
          <wsdlExtensions location="" singleFile="True" />
 <service name="MSB.CommercialExpress.API.Valuation.Services.PingService" behaviorConfiguration="BasicBehavior">
    <endpoint address=""
No matter what I change the location attribute to I get the original url. I'll take a look at the source but if you have an answer that would be great!

You have created a service.

To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:

svcutil.exe http://localhost:50138/Ping.svc?wsdl
You can also access the service description as a single file:



jrbogens wrote Jan 9, 2014 at 7:45 PM

never mind, I was expecting the url for the wsdl to change as well, it doesn't but the urls change within the wsdl as designed.