Soenneker.Flywheel.Communication 5.0.1

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Soenneker.Flywheel.Communication --version 5.0.1
                    
NuGet\Install-Package Soenneker.Flywheel.Communication -Version 5.0.1
                    
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="Soenneker.Flywheel.Communication" Version="5.0.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Soenneker.Flywheel.Communication" Version="5.0.1" />
                    
Directory.Packages.props
<PackageReference Include="Soenneker.Flywheel.Communication" />
                    
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 Soenneker.Flywheel.Communication --version 5.0.1
                    
#r "nuget: Soenneker.Flywheel.Communication, 5.0.1"
                    
#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 Soenneker.Flywheel.Communication@5.0.1
                    
#: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=Soenneker.Flywheel.Communication&version=5.0.1
                    
Install as a Cake Addin
#tool nuget:?package=Soenneker.Flywheel.Communication&version=5.0.1
                    
Install as a Cake Tool

Soenneker.Flywheel.Suite

Background jobs, Redis storage, source generators, and a live Blazor dashboard in one solution. Scaffolded with soenneker.nuget.builder.

Packages

Each project produces its own NuGet package. The suite is the repository and solution, not a combined runtime package.

Package Responsibility Flywheel dependencies
Soenneker.Flywheel.Communication Shared requests, responses, and typed hub contracts None
Soenneker.Flywheel.Core Job runtime, dashboard API, and hub Communication
Soenneker.Flywheel.Redis Redis job storage Core
Soenneker.Flywheel.Generators Compile-time job registration None; analyzer only
Soenneker.Flywheel.Dashboard Blazor components, typed consumer, and live client Communication

Dashboard does not bring Redis or the server runtime into WebAssembly. Projects reference each other directly in this solution; NuGet packing converts those references into separate package dependencies.

One demo

Install .NET 10 and run Redis 6.0.9 or newer on localhost:6379, then:

dotnet dev-certs https --trust
dotnet run --project demo/Soenneker.Flywheel.Demo

Open https://localhost:7443/ and sign in with admin / flywheel-demo in Development. Stop with Ctrl+C. The server hosts the WebAssembly client in demo/Soenneker.Flywheel.Dashboard.Demo; both use the source projects from this solution. See demo configuration.

Development

dotnet build Soenneker.Flywheel.Suite.slnx
dotnet test --project test/Soenneker.Flywheel.Dashboard.Tests

Redis integration tests use FLYWHEEL_TEST_REDIS, defaulting to localhost:16379. The performance runner is separate from the automated test projects. The product website is included under website/Soenneker.Flywheel.Website.

Dashboard pages use Lepton lifecycle management. A typed consumer handles API calls through the Flywheel API client, while a shared live client owns SignalR connections and subscriptions. Shared communication contracts keep the server and dashboard aligned. Dashboard navigation supports / and custom home paths, independently of the configured backend address.

Releases

build-and-test.yml builds the entire solution, runs the four test projects with Redis, publishes the hosted demo, and packs five separate packages. publish-package.yml calls that validation workflow and then runs a deployment matrix with one job per package, publishing to NuGet and GitHub Packages. A GitHub release is created only after every deployment succeeds.

All packages share 5.0.<publish workflow run number>. Local builds default to 5.0.0; BUILD_VERSION overrides it. The 5.0 series avoids collisions with independently versioned 4.0 releases and reflects the move of dashboard DTOs into Soenneker.Flywheel.Communication. Existing applications must update their response namespace imports accordingly.

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.
  • net10.0

    • No dependencies.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on Soenneker.Flywheel.Communication:

Package Downloads
Soenneker.Flywheel.Core

A durable background job processing, scheduling, and event execution runtime for .NET.

Soenneker.Flywheel.Dashboard

A real-time Blazor dashboard for monitoring and managing Soenneker Flywheel.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
5.0.7 0 9/8/2026
5.0.4 0 9/8/2026
5.0.3 0 9/8/2026
5.0.2 37 9/8/2026
5.0.1 35 9/8/2026