HangfireIO / HangfireIO/Hangfire
Discover IBackgroundProcess using IoC in non-AspNetCore
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
While the new AspNetCore implementation now got support for registering IBackgroundProcess as services and resolve them with support for DI, we still miss this in the non-AspNetCore implementation.
Is there any plans of doing this @odinserj or would you be interested in a pull request following the same pattern as AspNetCore?
https://github.com/HangfireIO/Hangfire/blob/master/src/Hangfire.AspNetCore/HangfireApplicationBuilderExtensions.cs#L68
Contributor guide
Research direction
Start with Hangfire.AspNetCore/HangfireApplicationBuilderExtensions.cs at the linked registration logic, then locate the corresponding non-AspNetCore startup path. Compare how IBackgroundProcess services are discovered and resolved, and confirm that the non-AspNetCore implementation supports the same dependency-injection behavior. Done means non-AspNetCore applications can register and resolve IBackgroundProcess implementations through IoC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100