Support for .NET 10 / planned release timeline

[imiljkovic]

Hi,

Thank you for the great project and continued maintenance of WorkflowCore.

I wanted to ask whether there is a planned release timeline for official .NET 10 support.

We encountered issues during workflow execution related to runtime expression compilation (InvalidProgramException coming from DefinitionLoader.BuildScalarInputAction).

Could you share:

• whether .NET 10 support is officially planned,
• if there is an ETA for a release,
• and whether there are known issues with dynamic expression compilation/workflow DSL on .NET 10?

Thanks!

[danielgerlag]

Hi, thanks for the report!

We've opened #1429 which adds .NET 10 to our test matrix and pre-compiles dynamic expressions outside closures in \DefinitionLoader\ (the pattern most likely to produce \InvalidProgramException\ on newer runtimes).

However, our existing unit tests pass on .NET 10 both before and after the fix, so we haven't been able to reproduce the exact failure you're seeing.

Could you share:

• The workflow definition (JSON or YAML) that triggers the \InvalidProgramException?
• The full stack trace?

That would let us add a targeted regression test and confirm the fix addresses your scenario. Thanks!

[danielgerlag]

Regarding the general .NET 10 support questions:

The core libraries (\WorkflowCore, \WorkflowCore.DSL, etc.) target
etstandard2.0, which means they are inherently compatible with any .NET runtime including .NET 10 no retargeting is needed.

With #1429 we're also adding
et10.0\ to our test projects so that our CI validates against .NET 10 going forward.

[imiljkovic]

@danielgerlag Thank you.

Here is the stack trace:

System.InvalidProgramException: Common Language Runtime detected an invalid program.
   at System.Runtime.CompilerServices.RuntimeHelpers.CompileMethod(RuntimeMethodHandleInternal method)
   at System.Runtime.CompilerServices.RuntimeHelpers.CompileMethod(RuntimeMethodHandleInternal method)
   at WorkflowCore.Services.DefinitionStorage.DefinitionLoader.<>c__DisplayClass14_0.<BuildScalarInputAction>g__acn|0(IStepBody pStep, Object pData, IStepExecutionContext pContext)
   at WorkflowCore.Services.WorkflowExecutor.ExecuteStep(WorkflowInstance workflow, WorkflowStep step, ExecutionPointer pointer, WorkflowExecutorResult wfResult, WorkflowDefinition def, CancellationToken cancellationToken)
   at WorkflowCore.Services.WorkflowExecutor.Execute(WorkflowInstance workflow, CancellationToken cancellationToken)

Here is the relevant step definition:

{
            "Id": "UpdateStatus",
            "Name": "Update internal status",
            "StepType": "...",
            "Inputs": {
                "MessageId": "data.MessageId",
                "Status": "\"waits-for-batching\""
            },
            "NextStepId": "WaitingForEvent"
        }

As you can see, this is just a simple variable binding and a string literal input.