web config - WCF Web Service Metadata Publishing Disabled Error -

I have my web The config has been modified to add a custom bond to boost buffer and message sizes, and it seems like to break the context of my behavioral element in order to make the service element explicitly.

< P> When I VS.S. I try to run my web service using the WCF Test client, or if I go to the service page, I get an error:

  Metadata publishing service is currently disabled for this  

I have compared this with some different sources from my web.config and everything seems to match. I do not know what is the problem

Here is the System.serviceModel element:

   & Lt; Endpoint address = "http: // localhost: 1895 / BIMIntegrationService.svc" binding = "custom binding" binding = configuration = "custombinding 0" contract = "bimantation ws.beb integration service" /> & Lt; / Services & gt; & Lt; / Services & gt; & Lt; Behavior & gt; & Lt; ServiceBehaviors & gt; & Lt; Transaction name = "metadataing" & gt; & Lt ;! - To avoid disclosing metadata information, set the value below to false and delete the metadata endpoint before deployment - & gt; & Lt; ServiceMetadata httpGetEnabled = "true" /> & Lt ;! - To get exception details in the flaws for debugging purposes, set the price below to true. To avoid exposing exception information, set it to false before deployment - & gt; & Lt; Service debug includes ExceptionDetailInFaults = "true" /> & Lt; / Behavior & gt; & Lt; / ServiceBehaviors & gt; & Lt; / Behavior & gt; & Lt; Binding & gt; & Lt; Custombinding & gt; & Lt; Binding name = "custombinding0" & gt; & Lt; BinaryMessageEncoding / & gt; & Lt; HttpTransport maxReceivedMessageSize = "262064" MaxbufrcSesize = "262064" Maxbepherpool Size = "262064" / & gt; & Lt; / Binding & gt; & Lt; / CustomBinding & gt; & Lt; / Binding & gt; & Lt; Service HostingInternet MultipleSitebindingsEnable = "True" aspNetCompatibilityEnabled = "true" />  

It seems that either web service page element is missing. I have not received any error in complaining that the targeted behavioral configuration is not present, or Anything like that, just metadata publishing is not enabled.

Any help would be greatly appreciated.

> Thank you.

I think I have "corrected" this issue. More coming later

Edit: To "fix" my problem, I used to add a new WCF service originally to my application, and it used to implement my previous interface, then I copied all the code from my original service and when I compromised the .config file (to see a lot like posting in a question), everything worked fine

Of course, I know, We all know that there is no magic here That is, there should be some discrepancies. This is when I saw / remembered that, when I had created my original service called "BIMIntegrationService.svc", I decided that it was too long a name, so I used to say "BIMIntegrationWS" for my class Changed the name. By doing this, however, the service file name does not change (and hence the name of the file in http: // address).

1) I changed:

   
 "BIMIntegrationWS.BIMIntegrationService" behavior configuration = "metadatabyver" & gt;  

to

  & lt; Service name = "BIMIntegrationWS.BIMIntegrationWS" behaviorConfiguration = "metadatabihair" & gt;  

After running the service in this manner, I got an error (at this time an assistant) complaining that if multiple site-bitbing was enabled, then the endpoint address should have been relative. Therefore:

2) I set it as a lie (because I do not remember why it is in the first place) and everything works fine.

I think I should take a hint when it seemed that my web service was not exactly using my "service" element: \

In fact, you In my second commentary in the original question, you can see that the auto-generated tag was indicating: "BIMIntegrationService". It was supposed to give it away.

I suspect that many others have the same problem, but only in case.