Wcf web.config file

Question

ok, my file has this structure.

<system.serviceModel> <services> <service name="ManyaWCF.ServiceManya" behaviorConfiguration="ServiceBehaviour"> <!-- Service Endpoints --> <!-- Unless fully qualified, address is relative to base address supplied above --> <endpoint address="" binding="webHttpBinding" contract="ManyaWCF.IServiceManya" behaviorConfiguration="web"> <!-- Upon deployment, the following identity element should be removed or replaced to reflect the identity under which the deployed service runs. If removed, WCF will infer an appropriate identity automatically. --> </endpoint> </service> </services> <behaviors> <serviceBehaviors> <behavior name="ServiceBehaviour"> <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment --> <serviceMetadata httpGetEnabled="true" /> <!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information --> <serviceDebug includeExceptionDetailInFaults="false" /> </behavior> </serviceBehaviors> <endpointBehaviors> <behavior name="web"> <webHttp /> </behavior> </endpointBehaviors> </behaviors> <serviceHostingEnvironment multipleSiteBindingsEnabled="true" /> </system.serviceModel> 

I got the same web.config in another wcf and worked as a champion, ofc with different folders and files. my folder structure is as follows.

When I try to play it, I get it,

  Service This is a Windows © Communication Foundation. The metadata publishing for this service is currently disabled. If you access the service, you can enable metadata publishing by completing the following steps to modify the configuration file or web application: 1. Create the following service behavior configuration, or add the item to a configuration <serviceMetadata> existing service behavior: <behaviors> <serviceBehaviors> <behavior name="MyServiceTypeBehaviors"> httpGetEnabled="true" <serviceMetadata /> </ Behavior> </ ServiceBehaviors> </ Behaviors> 2. Add the behavior configuration to the service: name="MyNamespace.MyServiceType" <service behaviorConfiguration="MyServiceTypeBehaviors"> Note: The service name must match the name of the configuration for the service implementation. 3. Add the following to end service configuration: binding="mexHttpBinding" contract="IMetadataExchange" <endpoint address="mex" /> Note: the service must have an http base address to add this. Here is an example of a service configuration file with metadata publishing enabled: <configuration> <system.serviceModel> <services> <! - Note: the service name must match the name of the configuration for the service implementation. -> name="MyNamespace.MyServiceType" <service behaviorConfiguration="MyServiceTypeBehaviors"> <! - Add the following end. -> <! - Note: the service must have an http base address to add this. -> binding="mexHttpBinding" contract="IMetadataExchange" <endpoint address="mex" /> </ Service> </ Services> <behaviors> <serviceBehaviors> <behavior name="MyServiceTypeBehaviors"> <! - Add the following item to the service behavior configuration. -> httpGetEnabled="true" <serviceMetadata /> </ Behavior> </ ServiceBehaviors> </ Behaviors> </ System.serviceModel> </ Configuration> For more information about publishing metadata, see the following documentation: http://go.microsoft.com/fwlink/?LinkId=65455 (may be in English). 

So, I made only 1 wcf and worked perfectly with the same web.conif. My luck from experience and knowledge about it kills me. Any clue?

thanks in advance.

Answer 1

As far as I know, you only need the endpoint with mexHttpBinding if you want to open WSDL for clients. Visual Studio (or wcfutil.exe) needs a WSDL description for creating webservice client classes.

After creating these webservice client classes, you no longer need to expose WSDL.

UPDATE: The <service> element in the configuration file should look like this:

 <service name="ManyaWCF.ServiceManya" behaviorConfiguration="ServiceBehaviour"> <endpoint address="" binding="webHttpBinding" contract="ManyaWCF.IServiceManya" behaviorConfiguration="web" /> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" /> </service> 

Answer 2

 <?xml version="1.0" encoding="UTF-8"?> <configuration> <system.web> <compilation debug="true" targetFramework="4.0" /> <httpRuntime maxRequestLength="1048576" executionTimeout="3600" /> </system.web> <appSettings> </appSettings> <connectionStrings> <add name="SQLConnect" connectionString="Your_Connection_String";User id=sa;Password=welcome3#"/> </connectionStrings> <system.serviceModel> <services> <service name="WCFRestService.RestServiceSvc" behaviorConfiguration="serviceBehavior"> <endpoint address="" bindingConfiguration="secureHttpBinding" binding="webHttpBinding" contract="WCFRestService.IRestServiceSvc" behaviorConfiguration="web"></endpoint> </service> </services> <behaviors> <endpointBehaviors> <behavior name="web"> <webHttp /> </behavior> </endpointBehaviors> <serviceBehaviors> <behavior name="serviceBehavior"> <serviceMetadata httpGetEnabled="true" /> <serviceDebug includeExceptionDetailInFaults="false" /> </behavior> <behavior name=""> <serviceMetadata httpGetEnabled="true" /> <serviceDebug includeExceptionDetailInFaults="false" /> </behavior> </serviceBehaviors> </behaviors> <bindings> <webHttpBinding> <binding name="secureHttpBinding" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" transferMode="Streamed"> </binding> </webHttpBinding> </bindings> <serviceHostingEnvironment multipleSiteBindingsEnabled="true" /> </system.serviceModel> <system.webServer> <modules runAllManagedModulesForAllRequests="true" /> <httpProtocol> <customHeaders> </customHeaders> </httpProtocol> <security> <requestFiltering> <requestLimits maxAllowedContentLength="1073741824" /> </requestFiltering> </security> <directoryBrowse enabled="true" /> </system.webServer> <system.web.extensions> <scripting> <webServices> <jsonSerialization maxJsonLength="50000000"/> </webServices> </scripting> </system.web.extensions> </configuration>