Update README.md

[lukevp]

• Add notes based on my testing with Redis.StackExchange at https://github.com/marcoCasamento/Hangfire.Redis.StackExchange and MemoryStorage.
• Add gotcha about ASP.NET Core DI unable to inject PerformContext into the constructor.

[pieceofsummer]

You can actually do that with a custom job activator:

public class InjectContextJobActivator : JobActivator
{
    private readonly IServiceScopeFactory _scopeFactory;
    
    public InjectContextJobActivator(IServiceScopeFactory scopeFactory)
    {
        _scopeFactory = scopeFactory ?? throw new ArgumentNullException(nameof(scopeFactory));
    }

    public override JobActivatorScope BeginScope(PerformContext context)
    {
        return new Scope(context, _scopeFactory.CreateScope());
    }

    private class Scope : JobActivatorScope, IServiceProvider
    {
        private readonly PerformContext _context;
        private readonly IServiceScope _scope;

        public Scope(PerformContext context, IServiceScope scope)
        {
            _context = context ?? throw new ArgumentNullException(nameof(context));
            _scope = scope ?? throw new ArgumentNullException(nameof(scope));
        }
        
        public override object Resolve(Type type)
        {
            return ActivatorUtilities.GetServiceOrCreateInstance(this, type);
        }

        object IServiceProvider.GetService(Type serviceType)
        {
            if (serviceType == typeof(PerformContext))
                return _context;
            return _scope.ServiceProvider.GetService(serviceType);
        }
    }
}

Just register it as a service in ConfigureServices:

services.AddSingleton<JobActivator, InjectContextJobActivator>();

[sommmen]

Just for future readers that have copied this code basically blindly, i just found out that because the serviceScope is not disposed this will cause a memory leak and possible myriad of other issues if your transient/scoped services are not cleaned up properly.

[sommmen]

I.e. add:

/// <inheritdoc />
public override void DisposeScope()
{
    _scope.Dispose();
}

[pieceofsummer]

I believe there were some issues with MemoryStorage due to incorrect implementation of Set related API. Was it fixed already?