Question

我有一个小型WCF客户端，我正在尝试通过应用程序配置文件配置服务发现 - 但每当我这样做时：

// Create a new DiscoveryClient instance from the 'DiscoveryEndpoint'
// configuration in App.config
DiscoveryClient discoveryClient = new DiscoveryClient("DiscoveryEndpoint");

我得到ArgumentNullException，Value cannot be null. Parameter name: contract。 contract构造函数的此重载没有DiscoveryClient参数，并且在App.config中正确指定了契约（参见下文）。

以下是App.config的相关部分：

<system.serviceModel>
  <client>
    <endpoint name="DiscoveryEndpoint"
              contract="IExampleContract"
              kind="dynamicEndpoint"
              endpointConfiguration="DynamicEndpointConfiguration"/>
  </client>

  <standardEndpoints>
    <dynamicEndpoint>
      <standardEndpoint name="DynamicEndpointConfiguration">
        <discoveryClientSettings>
          <endpoint kind="udpDiscoveryEndpoint"/>
          <findCriteria duration="00:00:02">
            <types>
              <add name="IExampleContract"/>
            </types>
            <scopes>
              <add scope="urn://wcf.test.com/examples/exampleContract/development"/>
            </scopes>
          </findCriteria>
        </discoveryClientSettings>
      </standardEndpoint>
    </dynamicEndpoint>
  </standardEndpoints>
</system.serviceModel>

这是使用Visual Studio 2010 SP1在.NET Framework 4.0上进行的。

DiscoveryClient(string)构造函数的此重载文档表明这应该创建一个新的DiscoveryClient实例，并在App.config中标识配置。

是否有其他人遇到过这种行为，如果有，你是如何解决的？

Answer 1

＆＃34; DiscoveryEndpoint＆＃34;您在配置文件中定义的实际上是服务客户端端点，而不是DiscoveryClient端点。

以下内容应该有效：

var exampleContractChannelFactory = new ChannelFactory<IExampleContract>("DiscoveryEndpoint");
var exampleContractClient = exampleContractChannelFactory.CreateChannel();
// You can now invoke methods on the exampleContractClient
// The actual service endpoint used by the client will be looked up dynamically 
// by the proxy using the DiscoveryClient class internally.

Answer 2

好的，我已经在启用了Enable .NET Framework source stepping选项的调试器中花了很多时间，并且我发现抛出此异常的原因（可能）是执行中的一个错误从配置文件中实例化DiscoveryClient的方式 - 在调用堆栈中有一个调用方式，它将硬编码值null传递给contract参数，这是抛出原始异常。

所以，经过多次头脑风暴和大量搜索之后，我提出了以下解决方法（好吧，更像是总HACK:！） - 我在这里发帖帮助任何人否则谁可能会遇到同样的问题。

// HACK: The following is a workaround for a bug in .NET Framework 4.0
//       Discovery should be possible when setup from the App.config with the
//       following three lines of code:
//
//         discoveryClient = new DiscoveryClient("DiscoveryEndpoint");
//         Collection<EndpointDiscoveryMetadata> serviceCollection = discoveryClient.Find(new FindCriteria(typeof(IExampleContract))).Endpoints;
//         discoveryClient.Close();
//
//       However, a bug in the Discovery Client implementation results in an
//       ArgumentNullException when running discovery in this way.
//
//       The following code overcomes this limitation by manually parsing the
//       standard WCF configuration sections of App.config, and then configuring
//       the appropriate FindCriteria for a programmatically configured discovery
//       cycle.  This code can be replaced by the above three lines when either
//         1. The bug in .NET Framework 4.0 is resolved (unlikely), or
//         2. The application is retargeted to .NET Framework 4.5 / 4.5.1
//
//       To aid future developers, this HACK will be extensively documented

// Load the App.config file into a ConfigurationManager instance and load the configuration
Configuration configuration = ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.None);

// Get the ServiceModel configuration group
ServiceModelSectionGroup serviceModelGroup = ServiceModelSectionGroup.GetSectionGroup(configuration);

// Get the StandardEndpoints configuration node
StandardEndpointsSection section = serviceModelGroup.StandardEndpoints;

// Get the DynamicEndpoint configuration node
Configuration dynamicEndpointConfiguration = section["dynamicEndpoint"].CurrentConfiguration;

// Get the first DynamicEndpoint configuration
// HACK: This assumes only one DynamicEndpoint configuration exists
//       No additional configurations will be interpreted.  This should
//       not pose a problem as typically a client will only access a
//       single service instance.  This can be extended if necessary
//       at a later time.
DynamicEndpointElement element = ((DynamicEndpointElement)serviceModelGroup.StandardEndpoints["dynamicEndpoint"].ConfiguredEndpoints[0]);

// Set the required Contract Type
// HACK: This is currently hard-coded to prevent the need to specify
//       an AssemblyQualifiedName in the App.config file.  This will
//       not typically pose a problem as each client will typically
//       only open a single service exposing a single, well-known,
//       Contract Type
FindCriteria criteria = new FindCriteria(typeof(IExampleContract));

// Add all required Scopes to the FindCriteria instance
foreach (ScopeElement scopeElement in element.DiscoveryClientSettings.FindCriteria.Scopes)
{
    criteria.Scopes.Add(scopeElement.Scope);
}

// Get the Discovery Duration
criteria.Duration = element.DiscoveryClientSettings.FindCriteria.Duration;

// Create a new Discovery Client instance
DiscoveryClient discoveryClient = new DiscoveryClient(new UdpDiscoveryEndpoint());

// Retrieve the matching Service Endpoints via Dynamic Search
Collection<EndpointDiscoveryMetadata> serviceCollection = discoveryClient.Find(criteria).Endpoints;

// Close the Discovery Client
discoveryClient.Close();

// HACK: END -- Process the results of Discovery

请注意，我假设在.NET Framework 4.5 / 4.5.1中已解决此问题 - 可能不是，但我目前无法测试。

如果其他人有替代解决方案，比这更优雅或更高效，请发布以帮助他人。

ServiceModel.Discovery.DiscoveryClient（string endpointConfigurationName）抛出ArgumentNullException

2 个答案: