Background: I'm maintaining an integration platform that pulls data from various unreliable APIs. Some of those actions generate potentially high costs, so for diagnostic purposes, every outgoing and incoming message is logged to disk to a separate file. For REST-like APIs, I use a simple wrapper on the network stream that also saves data to a file. For .NET Classic SOAP client, I have a helper that dynamically wraps SoapHttpClientProtocol
to use the same network stream logging mechanism.
With .NET Standard 2.0 and .NET Core, the only supported way to write SOAP clients is WCF. How do I programmatically configure WCF SOAP client to log the HTTP incoming/outgoing streams to separate files, preferrably with configurable names?
My current sample client code:
public abstract class ServiceCommunicatorBase<T>
where T : IClientChannel
{
private const int Timeout = 20000;
private static readonly ChannelFactory<T> ChannelFactory = new ChannelFactory<T>(
new BasicHttpBinding(),
new EndpointAddress(new Uri("http://target/endpoint")));
protected T1 ExecuteWithTimeoutBudget<T1>(
Func<T, Task<T1>> serviceCall,
[CallerMemberName] string callerName = "")
{
// TODO: fixme, setup logging
Console.WriteLine(callerName);
using (var service = this.CreateService(Timeout))
{
// this uses 2 threads and is less than ideal, but legacy app can't handle async yet
return Task.Run(() => serviceCall(service)).GetAwaiter().GetResult();
}
}
private T CreateService(int timeout)
{
var clientChannel = ChannelFactory.CreateChannel();
clientChannel.OperationTimeout = TimeSpan.FromMilliseconds(timeout);
return clientChannel;
}
}
public class ConcreteCommunicator
: ServiceCommunicatorBase<IWCFRemoteInterface>
{
public Response SomeRemoteAction(Request request)
{
return this.ExecuteWithTimeoutBudget(
s => s.SomeRemoteAction(request));
}
}