HostLoom.Locking.DependencyInjection
0.15.0
See the version list below for details.
dotnet add package HostLoom.Locking.DependencyInjection --version 0.15.0
NuGet\Install-Package HostLoom.Locking.DependencyInjection -Version 0.15.0
<PackageReference Include="HostLoom.Locking.DependencyInjection" Version="0.15.0" />
<PackageVersion Include="HostLoom.Locking.DependencyInjection" Version="0.15.0" />
<PackageReference Include="HostLoom.Locking.DependencyInjection" />
paket add HostLoom.Locking.DependencyInjection --version 0.15.0
#r "nuget: HostLoom.Locking.DependencyInjection, 0.15.0"
#:package HostLoom.Locking.DependencyInjection@0.15.0
#addin nuget:?package=HostLoom.Locking.DependencyInjection&version=0.15.0
#tool nuget:?package=HostLoom.Locking.DependencyInjection&version=0.15.0
HostLoom.Locking.DependencyInjection
This package registers the HostLoom.Locking kernel with
Microsoft.Extensions.DependencyInjection:
services
.AddHostLoomLocking(locking => locking.Namespace = "billing")
.UseInMemory()
.AddHealthChecks();
AddHostLoomLocking binds LockingOptions, validates them when the host starts with messages
that name the option key at fault, and registers IDistributedLock as a singleton composed from
the provider chosen on the builder. It works without AddHostLoom(); nothing here references the
messaging kernel. Repeated calls return a builder over the same registration, and every
registration is TryAdd, so an application can register its own TimeProvider or provider first.
Exactly one provider per service collection: UseInMemory() installs the per-process provider,
and a backend package such as HostLoom.Redis adds its own Use* extension over
UseProvider<TProvider>(name). A second Use* throws and names the provider already chosen. An
enabled lock with no provider fails startup validation; Locking:Enabled = false is single-instance
mode and needs none.
AddHealthChecks() registers a readiness check tagged ready that asks the provider's
ILockProviderHealthProbe whether the backend is reachable. A provider without a probe, including
the in-memory one, reports healthy with a description saying so. Liveness is never touched.
See the HostLoom.Locking package README for the contract, the retry policy, and the lost-lease
semantics.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- HostLoom.Locking (>= 0.15.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.12)
- Microsoft.Extensions.Diagnostics.HealthChecks (>= 10.0.12)
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.12)
- Microsoft.Extensions.Options (>= 10.0.12)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on HostLoom.Locking.DependencyInjection:
| Package | Downloads |
|---|---|
|
HostLoom.Redis
Redis backend for HostLoom caching and locking: one owned connection, a cache store, an invalidation channel, a lock provider, and health probes over StackExchange.Redis. |
|
|
HostLoom.Valkey
Standalone Valkey backend for HostLoom caching and coordination locks over ValkeyDotNet. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.17.0 | 0 | 10/25/2026 |
| 0.16.1 | 105 | 10/22/2026 |
| 0.16.0 | 180 | 10/14/2026 |
| 0.15.1 | 130 | 10/12/2026 |
| 0.15.0 | 127 | 10/4/2026 |
| 0.14.0 | 112 | 10/4/2026 |
| 0.13.0 | 110 | 9/28/2026 |
| 0.12.0 | 107 | 9/27/2026 |
| 0.11.0 | 108 | 9/25/2026 |
| 0.10.0 | 113 | 9/22/2026 |
| 0.9.0 | 107 | 9/22/2026 |
| 0.8.0 | 122 | 9/19/2026 |
| 0.7.0 | 118 | 9/17/2026 |
| 0.6.0 | 139 | 9/6/2026 |
| 0.5.0 | 124 | 9/5/2026 |
| 0.4.0 | 126 | 9/3/2026 |