ToolUp.Platform.Server.Jobs
0.40.0
Prefix Reserved
dotnet add package ToolUp.Platform.Server.Jobs --version 0.40.0
NuGet\Install-Package ToolUp.Platform.Server.Jobs -Version 0.40.0
<PackageReference Include="ToolUp.Platform.Server.Jobs" Version="0.40.0" />
<PackageVersion Include="ToolUp.Platform.Server.Jobs" Version="0.40.0" />
<PackageReference Include="ToolUp.Platform.Server.Jobs" />
paket add ToolUp.Platform.Server.Jobs --version 0.40.0
#r "nuget: ToolUp.Platform.Server.Jobs, 0.40.0"
#:package ToolUp.Platform.Server.Jobs@0.40.0
#addin nuget:?package=ToolUp.Platform.Server.Jobs&version=0.40.0
#tool nuget:?package=ToolUp.Platform.Server.Jobs&version=0.40.0
ToolUp.Platform.Server.Jobs
One part of the ToolUp server tier. It holds background work and delivery: the job store and scheduler with its handlers, the distributed lock seam, notifications, presence and co-editing, transactional notification dispatch and its preference filters, and webhooks.
Do I reference this package?
Usually not. Reference ToolUp.Platform.Server: it holds the composition root (ServerApp) and
references every part of the server tier, so one reference resolves all of them. Reference this
part directly only when you want this subsystem without the rest of the tier above it.
How the server tier is cut
The tier is one compile order cut into contiguous runs, one assembly per run. Each part references only the parts before it, so the build graph says which subsystem a change touched:
ToolUp.Platform.Server.RemotingToolUp.Platform.Server.InfraToolUp.Platform.Server.ConfigToolUp.Platform.Server.ScopeToolUp.Platform.Server.JobsToolUp.Platform.Server.AuditToolUp.Platform.Server: file management, the composition root, boot and preflight
This part depends on: Remoting, Infra, Config and Scope.
Namespaces
The cut moved no namespace. Code in this part keeps the namespaces it had inside
ToolUp.Platform.Server (ToolUp.Platform, ToolUp.Platform.Server, and the module paths beside them), so a consumer's open
lines compile unchanged whichever package they reference.
License
Apache-2.0. See the repository's LICENSE.
| 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
- FSharp.Core (>= 10.1.300)
- ToolUp.Platform.Server.Config (>= 0.40.0)
- ToolUp.Platform.Server.Infra (>= 0.40.0)
- ToolUp.Platform.Server.Remoting (>= 0.40.0)
- ToolUp.Platform.Server.Scope (>= 0.40.0)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on ToolUp.Platform.Server.Jobs:
| Package | Downloads |
|---|---|
|
ToolUp.Platform.Server
ToolUp.Platform Server — Giraffe-over-ASP.NET Core implementation surface: scope resolution, DI, default in-process implementations, ServerApp composition root, middleware. Depends on ToolUp.Platform.Core. The package references every part of the server tier (ToolUp.Platform.Server.Remoting, .Infra, .Config, .Scope, .Jobs and .Audit) and holds the composition root itself, so referencing it alone resolves the whole tier. |
|
|
ToolUp.Platform.Server.Audit
ToolUp.Platform server tier, Audit part: the audit log and its replication, artefact signing, field classification, consent, erasure, data-subject requests and evidence bundles. Referenced by ToolUp.Platform.Server, which most applications reference instead. |
GitHub repositories
This package is not used by any popular GitHub repositories.