NetFramework.Tasks.Management.Abstractions 1.0.3

NetTaskManagement

A .NET Standard 2.0 library for Task Parallel Library (TPL) orchestration with Dependency Injection support.

Tasks are identified by string key and managed through a status-based API — no raw Task objects exposed to callers. The library handles the full task lifecycle: register → start → cancel → check completion → delete, and exposes an append-only observability queue that captures disposal metadata for external monitoring.

NetTaskManagement vs TPL Dataflow — which one do you need?

These are complementary tools, not competing ones. The benchmarks below are meant to help you choose.

Choose NetTaskManagement (LongRunning) when your workers block (I/O, sleep, external calls) and N exceeds the thread-pool minimum — all workers start simultaneously with no injection delay.<br> Choose NetTaskManagement (None) when tasks are short-lived and pool availability is not a concern — lower startup cost with named handles and per-task lifecycle control.<br> Choose TPL Dataflow when you are processing a high-volume stream of anonymous items through a pipeline graph.

View live benchmark charts — NTM vs Dataflow

Packages

Installation

dotnet add package NetFramework.Tasks.Management

If you only need the ITaskManagement contract (e.g. in a project that wires up DI but doesn't consume the implementation directly):

dotnet add package NetFramework.Tasks.Management.Abstractions

Quick start

Register the service

services.AddTaskManagement();

Inject and use ITaskManagement

public class MyService
{
    private readonly ITaskManagement _tasks;

    public MyService(ITaskManagement tasks) => _tasks = tasks;

    public void RunJob(string jobName)
    {
        var cts = new CancellationTokenSource();

        _tasks.RegisterTask(jobName, state =>
        {
            var token = ((CancellationTokenSource)state).Token;
            while (!token.IsCancellationRequested)
            {
                // do work
            }
        }, cts);

        _tasks.StartTask(jobName);
    }

    public void CancelJob(string jobName) => _tasks.CancelTask(jobName);
}

API reference

All methods return TaskManagementStatus — an enum value instead of throwing exceptions for expected outcomes.

Status enum highlights

Observability queue

When DeleteTask(name, sendToQueue: true) is called, a TaskDisposedDataModel record (task name, id, final status, disposed flag) is appended to an internal ConcurrentQueue. Dequeue and forward it to your logging or monitoring platform however you like:

if (_tasks.DequeueTaskDisposedDataModel(out var record) == TaskManagementStatus.ObjectInfoDequeued)
{
    logger.LogInformation("Task {Name} (id={Id}) finished with status {Status}", 
        record.TaskName, record.TaskId, record.TaskStatus);
}

Benchmarks

Performance is tracked automatically on every push to main and published as interactive charts:

View benchmark charts

All benchmarks run on net8.0, net9.0, and net10.0 with [MemoryDiagnoser] enabled (reports allocated bytes per operation).

To run the comparison benchmarks locally (Release mode required):

dotnet run -c Release -f net9.0 --project benchmarks/NetFramework.Tasks.Management.Benchmarks/ -- --filter '*DataflowComparison*'

To run everything:

dotnet run -c Release -f net8.0 --project benchmarks/NetFramework.Tasks.Management.Benchmarks/ -- --filter '*'

See benchmarks/README.md for full run instructions and filter examples.

Examples

License

MIT © Jose Luis Guerra Infante