Skip to main content

WCF: Get the operation name within a Message Inspector

For logging purposes I needed to get the operation name of the called WCF service and the content of the message.

How can you get this done?

Important to notice when you look at the code is that I created an attribute and implement both the IDispatchMessageInspector and IServiceBehavior interface. This allows me to register this message inspector by just adding the attribute on top of my WCF service class.

/// <summary>
/// When applying this attribute to a service contract,
/// the input and output messages will be logged.
/// </summary>
[AttributeUsage(AttributeTargets.Class)]
public class MessageLoggingBehaviorAttribute : Attribute, IDispatchMessageInspector, IServiceBehavior
{
#region IDispatchMessageInspector Members

/// <summary>
/// Will be executed after a request is received.
/// </summary>
/// <param name="request">The request.</param>
/// <param name="channel">The channel.</param>
/// <param name="instanceContext">The instance context.</param>
/// <returns></returns>
/// <exception cref="System.Configuration.ConfigurationErrorsException">Throws a configuration exception if the environments don't match.</exception>
public object AfterReceiveRequest(ref System.ServiceModel.Channels.Message request, System.ServiceModel.IClientChannel channel, System.ServiceModel.InstanceContext instanceContext)
{
LogMessage(ref request);
return null;
}

/// <summary>
/// Will be executed before the reply is send.
/// </summary>
/// <param name="reply">The reply.</param>
/// <param name="correlationState">State of the correlation.</param>
public void BeforeSendReply(ref System.ServiceModel.Channels.Message reply, object correlationState)
{
LogMessage(ref reply);
}

#endregion

#region IServiceBehavior Members

/// <summary>
/// Adds the binding parameters.
/// </summary>
/// <param name="serviceDescription">The service description.</param>
/// <param name="serviceHostBase">The service host base.</param>
/// <param name="endpoints">The endpoints.</param>
/// <param name="bindingParameters">The binding parameters.</param>
public void AddBindingParameters(ServiceDescription serviceDescription, System.ServiceModel.ServiceHostBase serviceHostBase, System.Collections.ObjectModel.Collection<ServiceEndpoint> endpoints, System.ServiceModel.Channels.BindingParameterCollection bindingParameters)
{
}

/// <summary>
/// Applies the dispatch behavior.
/// </summary>
/// <param name="serviceDescription">The service description.</param>
/// <param name="serviceHostBase">The service host base.</param>
public void ApplyDispatchBehavior(ServiceDescription serviceDescription, System.ServiceModel.ServiceHostBase serviceHostBase)
{
foreach (ChannelDispatcher chDisp in serviceHostBase.ChannelDispatchers)
{
foreach (EndpointDispatcher epDisp in chDisp.Endpoints)
{
epDisp.DispatchRuntime.MessageInspectors.Add(new MessageLoggingBehaviorAttribute());
}
}
}

/// <summary>
/// Validates the specified service description.
/// </summary>
/// <param name="serviceDescription">The service description.</param>
/// <param name="serviceHostBase">The service host base.</param>
public void Validate(ServiceDescription serviceDescription, System.ServiceModel.ServiceHostBase serviceHostBase)
{
}

#endregion
}

Inside the AfterReceiveRequest and BeforeSendReply methods I call the LogMessage method passing the message object as a reference. Inside the log message I extract the operation name from the incoming headers, do a little bit of service location to get an IMessageLogger instance and invoke the log method in a separate task.

private void LogMessage(ref Message message) 
{
var action = OperationContext.Current.IncomingMessageHeaders.Action;
var operationName = action.Substring(action.LastIndexOf("/")+1);

var messageLogger = IoC.Container.Resolve<IMessageLogger>();
var messageContent = message.ToString();
Task.Factory.StartNew(() => messageLogger.Log(operationName, new List<string> { messageContent })); 
}

And as a last step I add this attribute to my service class.

[MessageLoggingBehavior]
[ServiceBehavior(InstanceContextMode = InstanceContextMode.PerCall)]
public class AanbiederService : IAanbiederService
{

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...