[Workflows] How to implement an Executor

[ecc-parity-check]

Hi,

I'm trying to follow the https://learn.microsoft.com/en-us/agent-framework/user-guide/workflows/core-concepts/executors?pivots=programming-language-csharp

but it doesn't seem to work.

Let's take the example from the guide:

internal sealed partial class UppercaseExecutor() : Executor("UppercaseExecutor")
{
    [MessageHandler]
    private ValueTask<string> HandleAsync(string message, IWorkflowContext context)
    {
        string result = message.ToUpperInvariant();
        return ValueTask.FromResult(result); // Return value is automatically sent to connected executors
    }
}

It gives me an error

So how can I implement this method, what should it do?

        protected override Microsoft.Agents.AI.Workflows.RouteBuilder ConfigureRoutes(Microsoft.Agents.AI.Workflows.RouteBuilder routeBuilder)
        {
            // Implementation ?
        }

[moonbox3]

Adding @lokitoth

[RorroRojas3]

Is there any updates on this? Facing the same issue. Any updates @moonbox3 @lokitoth?

[RorroRojas3]

@ecc-parity-check Update, I was able to fix it by providing the input and output to executor class

internal sealed partial class ResearchExecutor(AIAgent researchAgent) : Executor<WorkflowContextDto, WorkflowContextDto>(nameof(ResearchExecutor))
{
    private readonly AIAgent _researchAgent = researchAgent;

    [MessageHandler]
    public override async ValueTask<WorkflowContextDto> HandleAsync(WorkflowContextDto input, IWorkflowContext context, CancellationToken cancellationToken = default)
    {
        var response = await _researchAgent.RunAsync(input.Prompt, cancellationToken: cancellationToken);
        var result = JsonSerializer.Deserialize<ResearchOutputDto>(response.Text);
        input.ResearchOutput = result!;
        await context.QueueStateUpdateAsync(input.WorkflowId.ToString(), input, scopeName: "WorkflowState", cancellationToken);
        return input;
    }
}

[ecc-parity-check]

Yes, I'm doing the same as a workaround, but this is deprecated, so I would be more than happy to start implementing my logic in a more future proof way :)