I just created WCF.net 3.5 website, I think that using creting by default would be enough for replication. but it can be replicated. I have VS2013 with all the updates downloaded from my MSDN, and I have windows 8.1.
I have to say that a few months ago I had a problem on some machines, so others were resolved, and I assumed that it was related to the installation, but now it appears on three different machines, one of them with windows 8. all of there are 64 bits of them.
The service is perfectly executed, as it was until now, when I was delivered and in production, it works smoothly.
Now I created the base ASP.net aqlso.net 3.5. and tried to add a link to the service, and it shows the following message after it could not be added.
An error occurred while loading 'http: // localhost: 40226 / HabeasDataService.svc / _vti_bin / ListData.svc / $ metadata'. Request error with HTTP status 404: not found. The metadata contains a link that cannot be resolved: "http: // localhost: 40226 / HabeasDataService.svc". T The remote server returned an unexpected response: (405) Method not allowed. The remote server returned an error: (405) Method not allowed. If the service is defined in the current solution, try creating a solution and adding the link to the service again.
Of course, I did reconnect with the wedge, but the problem still persists.
Service configuration is as follows
<system.serviceModel> <services> <service behaviorConfiguration="ServicesLayer.Service1Behavior" name="ServicesLayer.Service1"> <endpoint bindingConfiguration="BigHttpBinding" name="BasicHttp" address="" binding="basicHttpBinding" contract="ServicesLayer.IHabeasDataService"> <identity> <dns value="localhost" /> </identity> </endpoint> <endpoint address="" binding="mexHttpBinding" contract="IMetadataExchange" /> </service> </services> <behaviors> <serviceBehaviors> <behavior name="ServicesLayer.Service1Behavior"> <!-- To avoid disclosing metadata information, set the value below to false 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="true"/> </behavior> </serviceBehaviors> </behaviors> <bindings> <basicHttpBinding> <binding name="BigHttpBinding" maxBufferSize="65536" maxBufferPoolSize="65536" maxReceivedMessageSize="65536" transferMode="Buffered"> <readerQuotas maxDepth="64" maxStringContentLength="65536" maxArrayLength="65536" maxBytesPerRead="4096" maxNameTableCharCount="32768"/> </binding> </basicHttpBinding> </bindings> </system.serviceModel>
I noticed this line:
<!-- To avoid disclosing metadata information, set the value below to false before deployment --> <serviceMetadata httpGetEnabled="true"/>
and try both configurations and still the same error.
When I try to run the svc file by clicking the view in the browser, I get 404.17 error like this.
This is very unpleasant, because it completely stops development.
Note Everything related to IIS may be useful, but remember that this is IIS Express. Switching to the local IIS in any case still fails, but, as I said. On a production server it's a mint