Package Guides¶
Compono ships as four independently-installable NuGet packages. Pick which ones you need before reading any single guide in depth — most projects only need the first two.
| Package | What it adds | Install if... |
|---|---|---|
Compono | The core composition engine: Composer, the resolution pipeline, and the source generator (embedded, no separate install). | Always — every other package depends on it. |
Compono.XunitV3 | [Compose]/[Compose<TProfile>] theory data attributes and [Shared] parameter sharing for xUnit v3. | You write xUnit v3 tests and want composed theory parameters instead of hand-built test data. |
Compono.NSubstitute | Automatic substitute composition for interface, delegate, and (optionally) abstract-class parameters. | Your composed types depend on interfaces you'd otherwise stub by hand with NSubstitute. |
Compono.Bogus | Realistic fake data — member-name-convention matching plus explicit Faker<T> sugar. | You want FullName/Email/StreetAddress-shaped fields to look like real data instead of anonymous strings. |
Every package targets net10.0/net11.0 and, until the first stable 1.0 release, publishes as a 0.x.y-preview.N prerelease — see Installation for the exact dotnet add package commands and why --prerelease is required.
Compono.Generators (the source generator itself) is not a separate package you install — it's embedded inside Compono.nupkg's analyzers/dotnet/cs and activates automatically once you reference Compono. See Compono for what that means in practice.
The common case¶
For most test projects, that's Compono + Compono.XunitV3:
Add Compono.NSubstitute and/or Compono.Bogus independently, as your tests need them — neither depends on the other, and both depend only on Compono, never on Compono.XunitV3 (composing plain object graphs with NSubstitute-provided substitutes or Bogus-generated data works the same whether or not you're also using xUnit v3 integration).
Version compatibility¶
All four packages ship in lockstep during the 0.x line — each integration package's dependency on Compono is exact-pinned at pack time, so mixing versions across packages (e.g. Compono.XunitV3 0.3.0 with Compono 0.5.0) is not supported and will fail to restore. Always update all installed Compono packages together — see ADR-0031 for the full 0.x versioning policy.