RevenueFlow 0.1.0-alpha.7.2

This is a prerelease version of RevenueFlow.
dotnet add package RevenueFlow --version 0.1.0-alpha.7.2
                    
NuGet\Install-Package RevenueFlow -Version 0.1.0-alpha.7.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="RevenueFlow" Version="0.1.0-alpha.7.2" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="RevenueFlow" Version="0.1.0-alpha.7.2" />
                    
Directory.Packages.props
<PackageReference Include="RevenueFlow" />
                    
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 RevenueFlow --version 0.1.0-alpha.7.2
                    
#r "nuget: RevenueFlow, 0.1.0-alpha.7.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 RevenueFlow@0.1.0-alpha.7.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=RevenueFlow&version=0.1.0-alpha.7.2&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=RevenueFlow&version=0.1.0-alpha.7.2&prerelease
                    
Install as a Cake Tool

RevenueFlow

Thin commerce composition package. Users, catalog, commerce, Payments, Events, Webhooks and transactional storage contracts are composed with the local RevenueFlow.Providers.Internal provider included by default. External payment providers, stores, worker hosting, authentication and HTTP endpoints remain application choices.

See the repository roadmap and support matrix for implemented versus planned features.

RevenueStoreBindings explicitly selects operational documents/users, current subscription queries, analytical writer/query/generation roles, and optional inbound publisher/consumer roles. One store package can implement several roles; use one PostgreSQL data source or separate operational and analytical sources. RevenueStoreCapability.Describe reflects actual implemented interfaces. No concrete store, queue or external payment provider is selected automatically, and role binding performs no I/O. The application owns disposal, schema initialization and the consistency of independently selected roles.

Supply totalsQueries explicitly in RevenueAnalyticsStoreBinding for large-audience native totals. The optional role and AnalyticsTotalsQueries capability are independent of bounded detailed reports.

configuration.CreateIssuance(scope) binds the internal provider for admin-issued gifts. The overload accepting Core's IRevenueIssuanceProvider replaces its pure planning capability. Issuing and renewing uses the same atomic commerce store; gift consideration records zero money while retaining frozen catalog terms. CreateRenewalTask() works with the existing optional RevenueReconciliationWorker; the host explicitly schedules it. See internal issuance for authorization, cancellation, catch-up and resource-retention semantics.

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.1.0-alpha.7.2 51 11/10/2026