WorkflowForge.Extensions.DependencyInjection 2.0.0

WorkflowForge.Extensions.DependencyInjection

Microsoft.Extensions.DependencyInjection integration for WorkflowForge

This extension provides seamless integration with Microsoft's dependency injection container, enabling:

• IOptions<T> pattern support
• Automatic configuration validation on startup
• ASP.NET Core integration
• Configuration binding from appsettings.json

📦 Installation

dotnet add package WorkflowForge.Extensions.DependencyInjection

Note: This package is optional. WorkflowForge core has zero dependencies and can be used standalone.

🚀 Quick Start

ASP.NET Core

// Program.cs or Startup.cs
public void ConfigureServices(IServiceCollection services)
{
    // Register logger (choose your implementation)
    services.AddSingleton<IWorkflowForgeLogger>(sp =>
        SerilogExtensions.CreateWorkflowForgeLogger());
    
    // Register WorkflowForge with configuration binding
    services.AddWorkflowForge(Configuration);
    
    // Register WorkflowSmith
    services.AddWorkflowSmith();
}

appsettings.json

{
  "WorkflowForge": {
    "MaxConcurrentWorkflows": 2,
    "ContinueOnError": false,
    "FailFastCompensation": false,
    "ThrowOnCompensationError": false,
    "EnableOutputChaining": true,
    "Middleware": {
      "Timing": {
        "Enabled": true,
        "IncludeDetailedTimings": false
      },
      "Logging": {
        "Enabled": true,
        "MinimumLevel": "Information",
        "LogDataPayloads": false
      },
      "ErrorHandling": {
        "Enabled": true,
        "RethrowExceptions": true,
        "IncludeStackTraces": true
      }
    }
  }
}

Usage in Controllers/Services

public class WorkflowService
{
    private readonly IWorkflowSmith _smith;
    private readonly IOptions<TimingMiddlewareOptions> _timingOptions;
    
    public WorkflowService(
        IWorkflowSmith smith,
        IOptions<TimingMiddlewareOptions> timingOptions)
    {
        _smith = smith;
        _timingOptions = timingOptions;
    }
    
    public async Task ExecuteWorkflow()
    {
        var workflow = new MyWorkflow();
        await _smith.ForgeAsync(workflow);
    }
}

🔧 Manual Configuration

If you don't use appsettings.json, you can configure options manually:

services.AddWorkflowForge(
    core =>
    {
        core.MaxConcurrentWorkflows = 2;
        core.ContinueOnError = false;
        core.EnableOutputChaining = true;
    },
    timing => timing.Enabled = false,
    logging => logging.MinimumLevel = "Warning",
    errorHandling => errorHandling.IncludeStackTraces = false
);

✅ Automatic Validation

This extension validates configuration on startup using the Validate() methods from options classes and registers IValidateOptions<WorkflowForgeOptions> for startup-time checks:

// This will throw on startup if configuration is invalid
services.AddWorkflowForge(configuration);

// Invalid configuration example:
{
  "WorkflowForge": {
    "MaxConcurrentWorkflows": -5,  // ❌ Throws: Must be between 0 and 10000
    "Middleware": {
      "Logging": {
        "MinimumLevel": "Verbose"  // ❌ Throws: Must be Trace/Debug/Information/Warning/Error/Critical
      }
    }
  }
}

Validation errors are caught at startup, not at runtime!

📚 API Reference

AddWorkflowForge(IConfiguration)

Binds configuration from appsettings.json and validates.

services.AddWorkflowForge(Configuration);

AddWorkflowForge(Actions)

Manually configure options.

services.AddWorkflowForge(
    core => { /* ... */ },
    timing => { /* ... */ },
    logging => { /* ... */ },
    errorHandling => { /* ... */ }
);

AddWorkflowSmith()

Registers IWorkflowSmith as a singleton.

Requirements:

• IWorkflowForgeLogger must be registered
• AddWorkflowForge() must be called first

services.AddSingleton<IWorkflowForgeLogger>(/* ... */);
services.AddWorkflowForge(Configuration);
services.AddWorkflowSmith(); // ✅ Now WorkflowSmith is available

🎯 Configuration Sections

🔍 Why This Extension Exists

WorkflowForge core has ZERO dependencies to avoid version conflicts when using extensions.

This extension provides optional DI integration for users who want:

• IOptions<T> pattern
• Configuration validation on startup
• ASP.NET Core integration
• appsettings.json binding

If you don't need these features, use WorkflowForge core directly!

📖 Related Packages

• WorkflowForge - Core workflow engine (zero dependencies)
• WorkflowForge.Extensions.Logging.Serilog - Serilog integration
• WorkflowForge.Extensions.Resilience.Polly - Polly resilience patterns
• WorkflowForge.Extensions.Observability.Performance - Performance metrics

📄 License

MIT License - Copyright © 2025-2026 AnimatLabs