How to log http level stream from WCF SOAP client on .NET Core?
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));
}
}
c# wcf soap .net-core .net-standard-2.0
add a comment |
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));
}
}
c# wcf soap .net-core .net-standard-2.0
1
I was working on the very same problem a week or two ago, there isn’t a lot of resources out there from what I could tell. Don’t have my computer with me, but I’ll be sure to post my solution whenever I get time!
– Joel
Nov 16 '18 at 16:14
Might’ve been a different problem I recall now but, I think I used: docs.microsoft.com/en-us/dotnet/api/… and then I sent along a message-header that way that I then filtered on the receiving end. Typing on my phone, sorry. I’ll elaborate more and post my solution on Monday! More info: docs.microsoft.com/en-us/dotnet/api/…
– Joel
Nov 16 '18 at 16:25
add a comment |
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));
}
}
c# wcf soap .net-core .net-standard-2.0
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));
}
}
c# wcf soap .net-core .net-standard-2.0
c# wcf soap .net-core .net-standard-2.0
asked Nov 16 '18 at 16:08
skolimaskolima
20.4k22101136
20.4k22101136
1
I was working on the very same problem a week or two ago, there isn’t a lot of resources out there from what I could tell. Don’t have my computer with me, but I’ll be sure to post my solution whenever I get time!
– Joel
Nov 16 '18 at 16:14
Might’ve been a different problem I recall now but, I think I used: docs.microsoft.com/en-us/dotnet/api/… and then I sent along a message-header that way that I then filtered on the receiving end. Typing on my phone, sorry. I’ll elaborate more and post my solution on Monday! More info: docs.microsoft.com/en-us/dotnet/api/…
– Joel
Nov 16 '18 at 16:25
add a comment |
1
I was working on the very same problem a week or two ago, there isn’t a lot of resources out there from what I could tell. Don’t have my computer with me, but I’ll be sure to post my solution whenever I get time!
– Joel
Nov 16 '18 at 16:14
Might’ve been a different problem I recall now but, I think I used: docs.microsoft.com/en-us/dotnet/api/… and then I sent along a message-header that way that I then filtered on the receiving end. Typing on my phone, sorry. I’ll elaborate more and post my solution on Monday! More info: docs.microsoft.com/en-us/dotnet/api/…
– Joel
Nov 16 '18 at 16:25
1
1
I was working on the very same problem a week or two ago, there isn’t a lot of resources out there from what I could tell. Don’t have my computer with me, but I’ll be sure to post my solution whenever I get time!
– Joel
Nov 16 '18 at 16:14
I was working on the very same problem a week or two ago, there isn’t a lot of resources out there from what I could tell. Don’t have my computer with me, but I’ll be sure to post my solution whenever I get time!
– Joel
Nov 16 '18 at 16:14
Might’ve been a different problem I recall now but, I think I used: docs.microsoft.com/en-us/dotnet/api/… and then I sent along a message-header that way that I then filtered on the receiving end. Typing on my phone, sorry. I’ll elaborate more and post my solution on Monday! More info: docs.microsoft.com/en-us/dotnet/api/…
– Joel
Nov 16 '18 at 16:25
Might’ve been a different problem I recall now but, I think I used: docs.microsoft.com/en-us/dotnet/api/… and then I sent along a message-header that way that I then filtered on the receiving end. Typing on my phone, sorry. I’ll elaborate more and post my solution on Monday! More info: docs.microsoft.com/en-us/dotnet/api/…
– Joel
Nov 16 '18 at 16:25
add a comment |
1 Answer
1
active
oldest
votes
I've managed to log messages using IClientMessageInspector
attached via a configurable behaviour. There's some documentation for Message Inspectors on MSDN but it's still vague (and somewhat out of date, netstandard-2.0
API surface is slightly different.
I had to move from using the ChannelFactory<T>
to using the actual generated proxy class. Working code (cut for brevity):
var clientChannel = new GeneratedProxyClient(
new BasicHttpBinding { SendTimeout = TimeSpan.FromMilliseconds(timeout) },
new EndpointAddress(new Uri("http://actual-service-address"));
clientChannel.Endpoint.EndpointBehaviors.Add(new LoggingBehaviour());
Service classes:
// needed to bind the inspector to the client channel
// other methods are empty
internal class LoggingBehaviour : IEndpointBehavior
{
public void ApplyClientBehavior(ServiceEndpoint endpoint, ClientRuntime clientRuntime)
{
clientRuntime.ClientMessageInspectors.Add(new LoggingClientMessageInspector());
}
}
internal class LoggingClientMessageInspector : IClientMessageInspector
{
public object BeforeSendRequest(ref Message request, IClientChannel channel)
{
var correlationId = Guid.NewGuid();
this.SaveLog(ref request, correlationId, "RQ");
return correlationId;
}
public void AfterReceiveReply(ref Message reply, object correlationState)
{
var correlationId = (Guid)correlationState;
this.SaveLog(ref reply, correlationId, "RS");
}
private void SaveLog(ref Message request, Guid correlationId, string suffix)
{
var outputPath = GetSavePath(suffix, correlationId, someOtherData);
using (var buffer = request.CreateBufferedCopy(int.MaxValue))
{
var directoryName = Path.GetDirectoryName(outputPath);
if (directoryName != null)
{
Directory.CreateDirectory(directoryName);
}
using (var stream = File.OpenWrite(outputPath))
{
using (var message = buffer.CreateMessage())
{
using (var writer = XmlWriter.Create(stream))
{
message.WriteMessage(writer);
}
}
}
request = buffer.CreateMessage();
}
}
}
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53341566%2fhow-to-log-http-level-stream-from-wcf-soap-client-on-net-core%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've managed to log messages using IClientMessageInspector
attached via a configurable behaviour. There's some documentation for Message Inspectors on MSDN but it's still vague (and somewhat out of date, netstandard-2.0
API surface is slightly different.
I had to move from using the ChannelFactory<T>
to using the actual generated proxy class. Working code (cut for brevity):
var clientChannel = new GeneratedProxyClient(
new BasicHttpBinding { SendTimeout = TimeSpan.FromMilliseconds(timeout) },
new EndpointAddress(new Uri("http://actual-service-address"));
clientChannel.Endpoint.EndpointBehaviors.Add(new LoggingBehaviour());
Service classes:
// needed to bind the inspector to the client channel
// other methods are empty
internal class LoggingBehaviour : IEndpointBehavior
{
public void ApplyClientBehavior(ServiceEndpoint endpoint, ClientRuntime clientRuntime)
{
clientRuntime.ClientMessageInspectors.Add(new LoggingClientMessageInspector());
}
}
internal class LoggingClientMessageInspector : IClientMessageInspector
{
public object BeforeSendRequest(ref Message request, IClientChannel channel)
{
var correlationId = Guid.NewGuid();
this.SaveLog(ref request, correlationId, "RQ");
return correlationId;
}
public void AfterReceiveReply(ref Message reply, object correlationState)
{
var correlationId = (Guid)correlationState;
this.SaveLog(ref reply, correlationId, "RS");
}
private void SaveLog(ref Message request, Guid correlationId, string suffix)
{
var outputPath = GetSavePath(suffix, correlationId, someOtherData);
using (var buffer = request.CreateBufferedCopy(int.MaxValue))
{
var directoryName = Path.GetDirectoryName(outputPath);
if (directoryName != null)
{
Directory.CreateDirectory(directoryName);
}
using (var stream = File.OpenWrite(outputPath))
{
using (var message = buffer.CreateMessage())
{
using (var writer = XmlWriter.Create(stream))
{
message.WriteMessage(writer);
}
}
}
request = buffer.CreateMessage();
}
}
}
add a comment |
I've managed to log messages using IClientMessageInspector
attached via a configurable behaviour. There's some documentation for Message Inspectors on MSDN but it's still vague (and somewhat out of date, netstandard-2.0
API surface is slightly different.
I had to move from using the ChannelFactory<T>
to using the actual generated proxy class. Working code (cut for brevity):
var clientChannel = new GeneratedProxyClient(
new BasicHttpBinding { SendTimeout = TimeSpan.FromMilliseconds(timeout) },
new EndpointAddress(new Uri("http://actual-service-address"));
clientChannel.Endpoint.EndpointBehaviors.Add(new LoggingBehaviour());
Service classes:
// needed to bind the inspector to the client channel
// other methods are empty
internal class LoggingBehaviour : IEndpointBehavior
{
public void ApplyClientBehavior(ServiceEndpoint endpoint, ClientRuntime clientRuntime)
{
clientRuntime.ClientMessageInspectors.Add(new LoggingClientMessageInspector());
}
}
internal class LoggingClientMessageInspector : IClientMessageInspector
{
public object BeforeSendRequest(ref Message request, IClientChannel channel)
{
var correlationId = Guid.NewGuid();
this.SaveLog(ref request, correlationId, "RQ");
return correlationId;
}
public void AfterReceiveReply(ref Message reply, object correlationState)
{
var correlationId = (Guid)correlationState;
this.SaveLog(ref reply, correlationId, "RS");
}
private void SaveLog(ref Message request, Guid correlationId, string suffix)
{
var outputPath = GetSavePath(suffix, correlationId, someOtherData);
using (var buffer = request.CreateBufferedCopy(int.MaxValue))
{
var directoryName = Path.GetDirectoryName(outputPath);
if (directoryName != null)
{
Directory.CreateDirectory(directoryName);
}
using (var stream = File.OpenWrite(outputPath))
{
using (var message = buffer.CreateMessage())
{
using (var writer = XmlWriter.Create(stream))
{
message.WriteMessage(writer);
}
}
}
request = buffer.CreateMessage();
}
}
}
add a comment |
I've managed to log messages using IClientMessageInspector
attached via a configurable behaviour. There's some documentation for Message Inspectors on MSDN but it's still vague (and somewhat out of date, netstandard-2.0
API surface is slightly different.
I had to move from using the ChannelFactory<T>
to using the actual generated proxy class. Working code (cut for brevity):
var clientChannel = new GeneratedProxyClient(
new BasicHttpBinding { SendTimeout = TimeSpan.FromMilliseconds(timeout) },
new EndpointAddress(new Uri("http://actual-service-address"));
clientChannel.Endpoint.EndpointBehaviors.Add(new LoggingBehaviour());
Service classes:
// needed to bind the inspector to the client channel
// other methods are empty
internal class LoggingBehaviour : IEndpointBehavior
{
public void ApplyClientBehavior(ServiceEndpoint endpoint, ClientRuntime clientRuntime)
{
clientRuntime.ClientMessageInspectors.Add(new LoggingClientMessageInspector());
}
}
internal class LoggingClientMessageInspector : IClientMessageInspector
{
public object BeforeSendRequest(ref Message request, IClientChannel channel)
{
var correlationId = Guid.NewGuid();
this.SaveLog(ref request, correlationId, "RQ");
return correlationId;
}
public void AfterReceiveReply(ref Message reply, object correlationState)
{
var correlationId = (Guid)correlationState;
this.SaveLog(ref reply, correlationId, "RS");
}
private void SaveLog(ref Message request, Guid correlationId, string suffix)
{
var outputPath = GetSavePath(suffix, correlationId, someOtherData);
using (var buffer = request.CreateBufferedCopy(int.MaxValue))
{
var directoryName = Path.GetDirectoryName(outputPath);
if (directoryName != null)
{
Directory.CreateDirectory(directoryName);
}
using (var stream = File.OpenWrite(outputPath))
{
using (var message = buffer.CreateMessage())
{
using (var writer = XmlWriter.Create(stream))
{
message.WriteMessage(writer);
}
}
}
request = buffer.CreateMessage();
}
}
}
I've managed to log messages using IClientMessageInspector
attached via a configurable behaviour. There's some documentation for Message Inspectors on MSDN but it's still vague (and somewhat out of date, netstandard-2.0
API surface is slightly different.
I had to move from using the ChannelFactory<T>
to using the actual generated proxy class. Working code (cut for brevity):
var clientChannel = new GeneratedProxyClient(
new BasicHttpBinding { SendTimeout = TimeSpan.FromMilliseconds(timeout) },
new EndpointAddress(new Uri("http://actual-service-address"));
clientChannel.Endpoint.EndpointBehaviors.Add(new LoggingBehaviour());
Service classes:
// needed to bind the inspector to the client channel
// other methods are empty
internal class LoggingBehaviour : IEndpointBehavior
{
public void ApplyClientBehavior(ServiceEndpoint endpoint, ClientRuntime clientRuntime)
{
clientRuntime.ClientMessageInspectors.Add(new LoggingClientMessageInspector());
}
}
internal class LoggingClientMessageInspector : IClientMessageInspector
{
public object BeforeSendRequest(ref Message request, IClientChannel channel)
{
var correlationId = Guid.NewGuid();
this.SaveLog(ref request, correlationId, "RQ");
return correlationId;
}
public void AfterReceiveReply(ref Message reply, object correlationState)
{
var correlationId = (Guid)correlationState;
this.SaveLog(ref reply, correlationId, "RS");
}
private void SaveLog(ref Message request, Guid correlationId, string suffix)
{
var outputPath = GetSavePath(suffix, correlationId, someOtherData);
using (var buffer = request.CreateBufferedCopy(int.MaxValue))
{
var directoryName = Path.GetDirectoryName(outputPath);
if (directoryName != null)
{
Directory.CreateDirectory(directoryName);
}
using (var stream = File.OpenWrite(outputPath))
{
using (var message = buffer.CreateMessage())
{
using (var writer = XmlWriter.Create(stream))
{
message.WriteMessage(writer);
}
}
}
request = buffer.CreateMessage();
}
}
}
answered Nov 21 '18 at 19:00
skolimaskolima
20.4k22101136
20.4k22101136
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53341566%2fhow-to-log-http-level-stream-from-wcf-soap-client-on-net-core%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I was working on the very same problem a week or two ago, there isn’t a lot of resources out there from what I could tell. Don’t have my computer with me, but I’ll be sure to post my solution whenever I get time!
– Joel
Nov 16 '18 at 16:14
Might’ve been a different problem I recall now but, I think I used: docs.microsoft.com/en-us/dotnet/api/… and then I sent along a message-header that way that I then filtered on the receiving end. Typing on my phone, sorry. I’ll elaborate more and post my solution on Monday! More info: docs.microsoft.com/en-us/dotnet/api/…
– Joel
Nov 16 '18 at 16:25