DKNet is a suite of independent .NET 10 NuGet packages for building enterprise applications around Domain-Driven Design and Onion Architecture. There is no framework to adopt wholesale and no single AddDKNet() call: each package registers itself and can be used on its own, so you pull in only what a given DbContext, API, or worker actually needs.

28 packages are published to NuGet. One more, Aspire.Hosting.ServiceBus, is source-only in this repository (<IsPackable>false</IsPackable>) and documented anyway — it is an Aspire shared project you reference from an AppHost directly. DKNet.EfCore.Repos and DKNet.EfCore.Repos.Abstractions, the older generic-repository packages, were removed outright; see Migrating-Repos-To-Specifications if you are upgrading off them.

• Getting Started Guide — prerequisites, installation, and a first working setup
• Configuration & Setup — how configuration composes across packages
• Architecture Guide — the rings, what depends on what, and the two end-to-end paths
• Agent skills (dknet-skills) — install with npx skills add baoduy/DKNet or claude plugin install dknet-skills@dknet so your coding agent knows every package

• API Reference — index into the per-package API documentation
• Examples & Recipes — runnable implementation examples
• FAQ — common questions and troubleshooting

• Changelog — version history and release notes
• Migration Guide — upgrading between versions and off retired packages
• Contributing Guide — how to contribute to the project
• Testing Strategy — test stack and coverage targets
• Security Policy — supported versions and vulnerability reporting

Sorted by the problem you have, not by namespace. Follow the link for the full API and gotchas.

Foundation utilities that sit at the bottom of the dependency graph and pull in nothing else from DKNet.

• DKNet.Fw.Extensions — framework-agnostic reflection, type, string, enum and DI-inspection helpers, plus fluent assembly/type scanning (TypeExtractors)
• DKNet.RandomCreator — cryptographically secure random string and character generation for passwords, tokens, and other secrets

Entity base classes, the specification pattern, and the SaveChanges interceptor pipeline everything else hangs off.

• DKNet.EfCore.Abstractions — the persistence-agnostic vocabulary every other DKNet.EfCore.* package builds on: entity base classes, domain-event contracts, and the attributes that steer audit, sequence, and mapping behaviour
• DKNet.EfCore.Extensions — the wiring layer: convention-based entity configuration, global query filters, data seeding, GUID v7 keys, SQL sequences, and the SnapshotContext the save hooks are built on
• DKNet.EfCore.Specifications — filter, includes, and order-by as one reusable object, executed through a single non-generic IRepositorySpec, plus a runtime dynamic predicate builder. The current, supported way to query and persist
• DKNet.EfCore.Hooks — a pluggable before/after-SaveChanges interceptor pipeline: one shared interceptor per DbContext type plus a pair of interfaces you implement
• DKNet.EfCore.Events — dispatches domain events raised by entities during SaveChanges, so a domain method never references a publisher or a bus
• DKNet.EfCore.AuditLogs — captures a structured, field-level change record for every created, updated, or deleted entity and hands the batch to publishers you register
• DKNet.EfCore.DataAuthorization — row-level, ownership-based authorization: an automatic global query filter on reads plus SaveChanges-time owner stamping on writes
• DKNet.EfCore.Encryption — transparent, column-level encryption for string properties, applied at the database boundary via a standard ValueConverter
• DKNet.EfCore.DtoGenerator — a Roslyn incremental source generator that emits DTO properties from an entity type at compile time
• DKNet.EfCore.Relational.Helpers — four DbContext extension methods for relational bookkeeping EF Core does not expose: table creation, connection access, table-name resolution, and table-existence checks

SlimMessageBus integration: CQRS contracts, automatic save, and the CRUD source generator.

• DKNet.SlimBus.Extensions — EF-free fluent command/query/event interfaces and a one-call MediatR-replacement setup
• DKNet.SlimBus.Extensions.EfCore — automatic SaveChanges after a successful write, and domain events forwarded onto the bus
• DKNet.SlimBus.Generators — emits a whole CRUD vertical slice (request records, handlers, endpoint registration) from [CrudCreate]/[CrudUpdate]/[CrudAction]-attributed entity members

Application-level services with no dependency on the EF Core packages.

• DKNet.Svc.BlobStorage.Abstractions — provider-agnostic IBlobService contract and shared model types
• DKNet.Svc.BlobStorage.AwsS3 — AWS S3 adapter that also works against S3-compatible services such as MinIO and Cloudflare R2
• DKNet.Svc.BlobStorage.AzureStorage — Azure Blob Storage adapter backed by Azure.Storage.Blobs
• DKNet.Svc.BlobStorage.Local — local-filesystem adapter that stores blobs under a configured root folder with path-traversal protection
• DKNet.Svc.Encryption — explicitly-invoked cryptography: AES-GCM and RSA encryption, RSA signing, HMAC and SHA hashing, and Base64/Base64URL helpers
• DKNet.Svc.PdfGenerators — converts HTML or Markdown into a PDF using headless Chromium (PuppeteerSharp) and Markdig, with page layout, header/footer, and margin control
• DKNet.Svc.Transformation — fills bracketed tokens in a template string from plain objects or string dictionaries by reflection

Start-up orchestration, minimal-API glue, and idempotency for web and API workloads.

• DKNet.AspCore.Extensions — host-populated request members, discovered and versioned endpoint groups, verb-to-command mappers, generic list/read/delete endpoints, and FluentResults-to-IResult conversion
• DKNet.AspCore.Tasks — implement IBackgroundTask, register it, and one BackgroundService runs every registered task once when the host starts
• DKNet.AspCore.Idempotency — an IEndpointFilter that recognises a client-supplied idempotency key, blocks the same operation from running twice, and replays or rejects the retry
• DKNet.AspCore.Idempotency.MsSqlStore — SQL Server-backed key store
• DKNet.AspCore.Idempotency.NpgsqlStore — PostgreSQL-backed key store
• DKNet.AspCore.Idempotency.RedisStore — Redis-backed key store using SET NX reservation and native key expiry, with no schema or migrations
• DKNet.AspCore.Idempotency.Relational — the shared EF Core building blocks the two relational stores derive from. Not referenced directly by application code

Infrastructure orchestration helpers for .NET Aspire AppHost projects.

• Aspire.Hosting.ServiceBus — adds the Azure Service Bus emulator as a resource inside an Aspire AppHost, so local work needs no shared cloud namespace. Source-only: it sets <IsPackable>false</IsPackable>, so reference the project from your AppHost rather than a NuGet package

Every ring of the onion is a separate package, and every dependency points inward. The Architecture Guide walks the same picture in detail, adds the package dependency graph, and traces a request and a domain event end to end.

1. Dependency inversion — inner rings never reference outer ones; the arrows above are real ProjectReference entries in src/.
2. Separation of concerns — one package, one responsibility, and no package that only exists to aggregate others.
3. Domain-centricity — business rules live in entity methods; DKNet.EfCore.Abstractions is the only package a domain model has to see.
4. Event-driven where it helps — domain events are queued on the entity and dispatched after the write commits, so a domain method never talks to a bus.
5. Specifications, not a repository per entity — one injected IRepositorySpec serves every entity type; the entity comes from the specification passed to each call.

1. Pick the packages you need — start from the Which package do I need? table above.
2. Read the ring it lives in — the Architecture Guide explains what a package can and cannot depend on.
3. Wire it up — Configuration & Setup covers the four registration conventions the packages share.
4. Copy a working example — Examples & Recipes, or the SlimBus.ApiEndpoints template in the DKNet.Templates repository.

Corrections and additions are welcome. Open an issue describing the problem, or send a pull request that follows the structure and voice of the surrounding pages — the canonical page structure is the Package Documentation Template; see also the Contributing Guide.

Every claim on these pages should be traceable to src/, a test, or a config file. If you find one that is not, that is a bug worth reporting in the DKNet repository.