0

Here is my understanding of how a wcf library project is hosted. Once you create a wcf library project you have your app.config as follows:

<?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="WcfLib.Service1">
        <host>
          <baseAddresses>
            <add baseAddress = "http://localhost:8732/Design_Time_Addresses/WcfLib/Service1/" />
          </baseAddresses>
        </host>
        <!-- Service Endpoints -->
        <!-- Unless fully qualified, address is relative to base address supplied above -->
        <endpoint address ="" binding="wsHttpBinding" contract="WcfLib.IService1">
          <!-- 
              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.
          -->
          <identity>
            <dns value="localhost"/>
          </identity>
        </endpoint>
        <!-- Metadata Endpoints -->
        <!-- The Metadata Exchange endpoint is used by the service to describe itself to clients. --> 
        <!-- This endpoint does not use a secure binding and should be secured or removed before deployment -->
        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
      </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>

You can simply create an empty console application project (just put a Console.ReadLine() in it), and add a reference to the previous project's assembly, and add the entire services tag as seen above. Now its hosted. It lives as long as that console application lives.

Note the pattern how the markup was written to make this work. Everything in the <services/> stands for a wcf service entity which is to be hosted. In this case hosting was done via conifugration via my console application.

I am looking at if I can follow a similar analogy for wcf service consumption. Can I write my wcf client using the same pattern of configuration? Ultimately I am looking at putting those configurations in a separate config file.

Here are links of previous posts if you are interested in what made me ask this question

4

2 回答 2

1

您的服务不会自行托管。当您调试 WCF 库时，WCF 服务主机由调试器运行以托管您的服务。您必须在真实环境中手动执行此操作。

在此处阅读有关 WCF 服务主机的信息。

编辑：

并回答您的问题：是的，您可以以相同的方式配置您的客户端。看这篇文章

于 2012-05-28T08:40:30.060 回答
0

我遇到了以下SO帖子。也许我的答案就在于此……我不确定

如何告诉 WCF 客户端从不同的配置文件中读取设置？

于 2012-05-29T04:44:30.357 回答