Sekiban.Dcb.Core.Testing 10.4.0

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

Sekiban.Dcb.Core.Testing

The volatile in-memory stores and helpers Sekiban's own tests are built on, in a package a runtime project has no reason to reference.

They used to be available only from Sekiban.Dcb.Core, in the Sekiban.Dcb.InMemory namespace, where nothing stopped a production host from composing itself out of them — and something didn't. A production system registered the in-memory executor as its ISekibanExecutor, every command succeeded, and no event ever reached the database it had configured.

What this package changes, precisely. These types now have a home a runtime project has no reason to reference: the Sekiban.Dcb.Testing entry points require this package, so a project without it cannot reach them. What it does not do is take the old ones away — Sekiban.Dcb.InMemory remains public in Sekiban.Dcb.Core for compatibility, and code that already uses it still compiles and still runs. The protection against that path is the [Obsolete] pointer, and the opt-in AddSekibanDcbProductionGuard(), whose two answers are not the same answer: an in-process executor is rejected in Production, always — there is no override for it, whichever name it was obtained under — while a volatile store is rejected by default but can be authorised by the named, storage-only AllowVolatileStorageInProduction. A store that will not say what it is (Unknown) stays fail-closed either way. The compile-time boundary is a wall around the new door, not around the old one; the old one closes at the next major.

using Sekiban.Dcb.Testing;

var eventStore = new InMemoryEventStore(domainTypes.EventTypes);

The old Sekiban.Dcb.InMemory types still work and still behave identically — they are [Obsolete], not removed, and they will not be removed before the next major version. Nothing you have breaks today.

Do not reference this package from a runtime project. If you want a local development environment that behaves like production, the answer is a single-silo localhost Orleans host, not an in-memory executor — see the localhost Orleans composition guide.

Product Compatible and additional computed target framework versions.
.NET net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  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 (2)

Showing the top 2 NuGet packages that depend on Sekiban.Dcb.Core.Testing:

Package Downloads
Sekiban.Dcb.WithResult.Testing

Sekiban DCB WithResult Testing - the in-process testing executor for the ResultBox facade. Never reference this from a runtime project.

Sekiban.Dcb.WithoutResult.Testing

Sekiban DCB WithoutResult Testing - the in-process testing executor for the exception-based facade. Never reference this from a runtime project.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
10.6.0 0 7/18/2026
10.5.0 37 7/17/2026
10.4.0 104 7/14/2026