WcfClient.Dynamic 8.0.0-alpha

WcfClient.Dynamic

This package simplifies the process of consuming web endpoints of SOAP style, allowing dynamic (re)configuration of endpoint address, binding type, and all related data within appsettings. Incoming and outgoing messages, as well as other properties, can be configured using this package.

Installation

The package may be installed with the following commands:

• Using the .NET CLI:

dotnet add package WcfClient.Dynamic --latest

• Using Package Manager:

NuGet\Install-Package WcfClient.Dynamic --latest

Configuration

In the startup.cs or in the program.cs class, add the following line of code to configure a WCF client for consuming the desired web service:

services.AddWcfGenericClient<WebServiceInterface, Settings>(configurationSectionName)

where Settings is a SoapSettings class or any other class that derives from it.

The configuration section in the appsettings file may take one of the following forms:

"ConfigurationSectionName": {
  "OutgoingMessageHeaders": {
    "Headers": [
      {
        "Key": "HeaderName",
        "Value": "HeaderValue",
        "Ns": "Namespace"
      }
    ]
  },
  "OutgoingMessageProperties": {
    "Headers": [
      {
        "Key": "PropertyName",
        "Value": "PropertyName",
        "Ns": "Namespace"
      }
    ]
  },
  "IncomingMessageHeaders": {
    "Headers": [
      {
        "Key": "HeaderName",
        "Value": "HeaderValue",
        "Ns": "Namespace"
      }
    ]
  },
  "IncomingMessageProperties": {
    "Headers": [
      {
        "Key": "PropertyName",
        "Value": "PropertyValue",
        "Ns": "Namespace"
      }
    ]
  },
  "SoapClient": {
    // Binding section here ...
    // ...
    "EndpointConfiguration": 1
  }
}

Note that OutgoingMessageHeaders, OutgoingMessageProperties, IncomingMessageHeaders and IncomingMessageProperties sections are optional.

Allowed bindings

Each binding has these properties in common:

{
    "EndpointAddress": "https://{service-address}.asmx",
      "Name": "binding-name",
      "NamespaceIdentifier": "ns",
      "CloseTimeout": 60000,
      "OpenTimeout": 60000,
      "ReceiveTimeout": 60000,
      "SendTimeout": 60000
}

The following bindings may be declared in the "Binding" section:

• BasicHttpsBinding:

"SoapHttpsBinding": {
    // Common binding properties not included here for the sake of simplicity and readability
    "AllowCookies": true,
    "BypassProxyOnLocal": true,
    "MaxBufferSize": null,
    "MaxBufferPoolSize": null,
    "MaxReceivedMessageSize": null,
    "TransferMode": null,
    "UseDefaultWebProxy": null,
    "HostNameComparisonMode": null,
    "BasicHttpsSecurityMode": 0,
    "WSMessageEncoding": 1
}

For more information, inspect the SoapHttpsBinding class.

• BasicHttpBinding;
• NetHttpBinding;
• NetHttpsBinding;
• NetNamedPipeBinding;
• NetTcpBinding;
• WSHttpBinding;
• Ws2007HttpBinding;
• WsFederationHttpBinding.

Usage

The WCF client may be injected into the specified service via:

1. IGenericWcfClient<WebServiceInterface> wcfClient;
2. Func<Settings, WcfClient<WebServiceInterface>> factoryMethod.

If you choose the second option, it will be necessary to inject the following lines into the constructor's declaration of your service implementation:

• Func<WcfClient<WebServiceInterface>, OperationContextScope> scopeSelector;
• IOptionsSnapshot<Settings> settings;

The consumption of the web service would look like this:

var result = await _wcfClient.CallAsync(x => 
{
    return x.Service.GetInfoAsync(new GetInfoRequest());
}

or

using (var client = _factoryMethod(_settings.Value))
{
    using (var scope = _scopeSelector(client))
    {
        // apply message's incomming/outcomming headers/properties here
        // ...

        return client.Service.GetInfoAsync(new GetInfoRequest());
    }
}