I'm not exactly sure how these addresses work. But it think it is related to an address somewhere.
I'm using a console app to test the service. I've never had problems with the service until i tried using the IIS port.
Here is my app.config file of the console app. The top address and port number is the ASP.NET Dev Server port. The second one is the IIS port.
<?xml version="1.0" encoding="utf-8" ?> <configuration> <system.serviceModel> <bindings> <wsHttpBinding> <binding name="WSHttpBinding_IWebService" /> </wsHttpBinding> </bindings> <client> <!-- <endpoint address="http://localhost:5182/Service.svc" binding="wsHttpBinding"--> <endpoint address="http://localhost:9876/Service.svc" binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_IWebService" contract="MyWCF_ServiceReference.IWebService" name="WSHttpBinding_IWebService"> <identity> <dns value="localhost" /> </identity> </endpoint> </client> </system.serviceModel> </configuration>
Click on the images to see a bigger picture.
This is the error mesage:
Is there a reason why the address below is different from the previous ones?
http:// localhost:8732 /Design_Time_Addresses/WCFServiceLibrary/WebService/mex
This is where it is crashing for some unknown reason.
This shows that at the WCF Service itself, the ValidPerson is actually working.
Here is the conf file its running on.