Outer context for job execution by UnitOfWorkManager.

[itmagination]

UnitOfWorkManager provides outer context for job execution which is useful for scopes management (database transactions, DI container scopes etc.) and for externalization of any other kind of repetitive code on begin or end of each executed task.

To use UnitOfWorkManager you have to implement interface IUnitOfWorkManager and provide your implementation to Hangfire configuration. This is very similar to JobActivator usage.

For example to create WindorContainer scope for each job execution context you can use blow implementation:

class WindsorContainerScopeUnitOfWorkManager : IUnitOfWorkManager
{
  private readonly IWindsorContainer _container;

  public WindsorContainerScopeUnitOfWorkManager(IWindsorContainer container)
  {
     _container = container;
  }

  public object Begin()
  {
    return _container.BeginScope();
  }

  public void End(object context, Exception ex = null)
  {
    ((IDisposable) context).Dispose();
  }
}

And register it in Hangfire like below:

app.UseHangfire(config =>
{
    config.UseActivator(new WindsorJobActivator(_container.Kernel));
    config.UseUnitOfWorkManager(new WindsorContainerScopeUnitOfWorkManager(_container));
});

[odinserj]

Hi @itmagination, sorry for the looong delay 😦 In Hangfire 1.5.0-beta1 I've added the JobActivator.BeginScope method as well as the base JobActivatorScope class to allow support for custom scopes/child containers without any job filters to simplify the user experience. Please see my answer on a corresponding forum topic for some details.

I'm closing this PR. Thank you for it, you shown the way how to solve this problem using current features to many users! ❤️