WCF/WF - EndPointNotFoundException - Asked By Hamit YILDIRIM on 01-Dec-11 06:24 PM

I am newbie with WCF and my WCF giving me an error like that

EndPointNotFoundException : There was no endpoint listening at http://localhost: ...

WCF Library app.config below


<?xml version="1.0" encoding="utf-8" ?>
<configuration>


  <system.web>
    <compilation debug="true" />
  </system.web>
  <!-- When deploying the service library project, the content of the config file must be added to the host's 
  app.config file. System.Configuration does not support config files for libraries. -->
  <system.serviceModel>
    <services>
      <service name="TT.CMS.WCFLibrary.ExpediaServiceProvider">
        <endpoint address="" binding="wsHttpBinding" contract="TT.CMS.WCFLibrary.IExpediaServiceProvider">
          <identity>
            <dns value="localhost" />
          </identity>
        </endpoint>
        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
        <host>
          <baseAddresses>
            <add baseAddress="http://localhost:8732/Design_Time_Addresses/TT.CMS.WCFLibrary/Service1/" />
          </baseAddresses>
        </host>
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior>
          <!-- 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>
    </behaviors>
  </system.serviceModel>


</configuration>

and Client app.config below

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <system.serviceModel>
        <bindings>
            <wsHttpBinding>
                <binding name="WSHttpBinding_IExpediaServiceProvider" closeTimeout="00:01:00"
                    openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
                    bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard"
                    maxBufferPoolSize="524288" maxReceivedMessageSize="65536"
                    messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true"
                    allowCookies="false">
                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
                        maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                    <reliableSession ordered="true" inactivityTimeout="00:10:00"
                        enabled="false" />
                    <security mode="Message">
                        <transport clientCredentialType="Windows" proxyCredentialType="None"
                            realm="" />
                        <message clientCredentialType="Windows" negotiateServiceCredential="true"
                            algorithmSuite="Default" />
                    </security>
                </binding>
            </wsHttpBinding>
        </bindings>
        <client>
            <endpoint address="http://localhost:8732/Design_Time_Addresses/TT.CMS.WCFLibrary/Service1/"
                binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_IExpediaServiceProvider"
                contract="ExpediaTestClient.IExpediaServiceProvider" name="WSHttpBinding_IExpediaServiceProvider">
                <identity>
                    <dns value="localhost" />
                </identity>
            </endpoint>
        </client>
    </system.serviceModel>
</configuration>

I find the main couse in my position that is interesting with serverside code that is in my library. it wasnt found orginal connectionstring while looking to the entity framework.. (but this error code is not enough to identify current statement) Also i have not used ObjectContext before. what is best pattern or what is best practice in my position i dont know. 

if is there anyone who came across this necessaty. i will be very gratefull :)

thank you
Asked By Hamit YILDIRIM on 05-Dec-11 01:48 AM
Thanks for the reply..
I have solved this problem. I found that usefull improvements
1- Entity frameworks connectingstring must be stay on caller projects
2- If we dont share our entity instances than we have to return new entities, interesting anti patterns.

In ny case when wcf lib. Project came to the diployment phase than we have to remove app.config from wcf library.

Thanks again..