From 3284d6484525aa9ac530fc6d6a23d5d2bd9fccb1 Mon Sep 17 00:00:00 2001 From: Luke Paireepinart Date: Mon, 1 Jul 2019 09:55:31 -0500 Subject: [PATCH] Update README.md 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. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bc147ef..9c308cf 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Inspired by AppVeyor, Hangfire.Console provides a console-like logging experienc ## Features - - **Provider-agnostic**: (allegedly) works with any job storage provider (currently tested with SqlServer and MongoDB). + - **Provider-agnostic**: (allegedly) works with any job storage provider (currently tested with SqlServer, MemoryStorage, Redis.StackExchange and MongoDB). - **100% Safe**: no Hangfire-managed data (e.g. jobs, states) is ever updated, hence there's no risk to corrupt it. - **With Live Updates**: new messages will appear as they're logged, as if you're looking at real console. - (blah-blah-blah) @@ -58,7 +58,7 @@ Here's what you can configure: Hangfire.Console provides extension methods on `PerformContext` object, hence you'll need to add it as a job argument. -**NOTE**: Like `IJobCancellationToken`, `PerformContext` is a special argument type which Hangfire will substitute automatically. You should pass `null` when enqueuing a job. +**NOTE**: Like `IJobCancellationToken`, `PerformContext` is a special argument type which Hangfire will substitute automatically. You should pass `null` when enqueuing a job. It is not currently possible to use constructor injection for the PerformContext in ASP.NET Core. Now you can write to console: