Hi@danielgerlag, I found an issue in the Conductor.Domain.csproj:
Packages Microsoft.Extensions.DependencyInjection.Abstractions v3.1.0, Microsoft.Extensions.Logging.Abstractions v3.1.0, SharpYaml v1.6.5, StackExchange.Redis v2.0.601 and WorkflowCore v3.2.2 transitively introduce 90 dependencies into conductor’s dependency graph (see dependency graph before upgrades), while Microsoft.Extensions.DependencyInjection.Abstractions v3.1.13, Microsoft.Extensions.Logging.Abstractions v3.1.13, SharpYaml v1.6.6, StackExchange.Redis v2.1.0 and WorkflowCore v3.5.0 can only introduce 52 dependencies (see dependency graph after upgrades).
These upgrades can help project minimize the size of dependency graph.
Hope the PR can help you.
Hi@danielgerlag, I found an issue in the Conductor.Domain.csproj:
Packages Microsoft.Extensions.DependencyInjection.Abstractions v3.1.0, Microsoft.Extensions.Logging.Abstractions v3.1.0, SharpYaml v1.6.5, StackExchange.Redis v2.0.601 and WorkflowCore v3.2.2 transitively introduce 90 dependencies into conductor’s dependency graph (see dependency graph before upgrades), while Microsoft.Extensions.DependencyInjection.Abstractions v3.1.13, Microsoft.Extensions.Logging.Abstractions v3.1.13, SharpYaml v1.6.6, StackExchange.Redis v2.1.0 and WorkflowCore v3.5.0 can only introduce 52 dependencies (see dependency graph after upgrades).
These upgrades can help project minimize the size of dependency graph. Hope the PR can help you.
Best regards, sucrose