Intropy.Framework.Hosting 0.3.0-beta.2

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
This is a prerelease version of Intropy.Framework.Hosting.
There is a newer prerelease version of this package available.
See the version list below for details. 
dotnet add package Intropy.Framework.Hosting --version 0.3.0-beta.2
                    


                    

                
NuGet\Install-Package Intropy.Framework.Hosting -Version 0.3.0-beta.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Intropy.Framework.Hosting" Version="0.3.0-beta.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Intropy.Framework.Hosting" Version="0.3.0-beta.2" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Intropy.Framework.Hosting" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Intropy.Framework.Hosting --version 0.3.0-beta.2
                    


                    

                
#r "nuget: Intropy.Framework.Hosting, 0.3.0-beta.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Intropy.Framework.Hosting@0.3.0-beta.2
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Intropy.Framework.Hosting&version=0.3.0-beta.2&prerelease
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Intropy.Framework.Hosting&version=0.3.0-beta.2&prerelease
                    


                            Install as a Cake Tool

Intropy.Framework.Hosting

Runtime orchestration for Intropy.Framework pipelines.

Handles the integration host lifecycle: waits for the Dapr sidecar, runs the pipeline, subscribes to message topics, applies idle timeouts, and shuts down cleanly.

Install

dotnet add package Intropy.Framework.Hosting

Requirements

A Dapr sidecar. Used together with Intropy.Framework.Blocks to run TransactionalIntegration and similar long-running pipelines.

Run-to-completion jobs

RunToCompletionRunner hosts workloads that do one sweep and exit — scheduled externally (system host locally, Kubernetes CronJob in production). It waits for the sidecar, executes an IRunToCompletionJob inside a traced activity, shuts the sidecar down (bounded, so a wedged sidecar cannot hang the job), and maps the outcome to an exit code.

Jobs are expected to be idempotent. Implement IRunToCompletionJob and return a JobRunSummary:

public class MyExtractorJob : IRunToCompletionJob
{
    public async Task<JobRunSummary> ExecuteAsync(CancellationToken ct)
    {
        // ... one sweep of work ...
        return new JobRunSummary(Processed: 42, Failed: 0, Cancelled: 3);
    }
}

Wire it up in Program.cs. The component owns the cancellation token (e.g. SIGTERM wiring); the framework deliberately does not abstract console-host plumbing.

var services = new ServiceCollection();
services.AddDaprClient();
services.AddRunToCompletionJob<MyExtractorJob>(o => o.JobName = "my-extractor");

await using var provider = services.BuildServiceProvider();
return await provider.GetRequiredService<RunToCompletionRunner>().RunAsync(ct);

AddRunToCompletionJob registers the job as a singleton if you haven't. Register it yourself first if you need control over construction — your registration takes precedence.

Exit codes

Code Meaning
0 Success, nothing to do, or cancelled. Cancellation is success by design: the job is idempotent and decided it does not need to process (e.g. duplicates detected), so the scheduler must not retry.
1 Job failure: the job threw, or JobRunSummary.Failed was greater than zero.
2 Infrastructure failure: the Dapr sidecar never became available. The job never ran.

A failed sidecar shutdown is logged but never changes the exit code — the job's outcome stands.

Counting cancelled items

The framework cannot infer duplicate detection — component code must count StepResult<T>.Cancelled outcomes itself and report them in JobRunSummary.Cancelled. Cancelled items never affect the exit code, but keep the summary log line and trace tags honest.

License

MIT. See the repository for source and documentation.

Product 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.3.0-beta.5 52 8/12/2026
0.3.0-beta.4 63 8/11/2026
0.3.0-beta.3 58 8/11/2026
0.3.0-beta.2 55 8/11/2026
0.3.0-beta.1 59 8/11/2026
0.2.3 117 5/27/2026
0.2.2 123 5/26/2026
0.1.1 125 5/25/2026
0.1.0 116 5/18/2026