DKNet.Templates

DKNet.Minimal.Template Documentation

Reference docs for the DKNet.Minimal.Template — a NuGet solution template that scaffolds production-ready .NET 10 microservices using vertical-slice DDD/CQRS.

Getting started

• Template Usage Reference — install the template, scaffold a solution, then run, test, and publish it.
• Template Feature List — everything dotnet new dknet-minimal wires up before you write feature code.
• DKNet Package Inventory — the DKNet NuGet family, one package per capability.
• Configuration Reference — every appsettings key a generated solution reads: meaning, default, effect, and the code path that reads it.
• Extension Points — where your own code attaches, and the boundaries the architecture tests hold you to.

Building a feature

• DDD Implementation Guide — add one vertical-slice feature, entity to endpoint.
• CRUD Attributes — build a full CRUD slice from four attributes, domain actions included (generator-driven).
• Querying and Specifications — the read side, from HTTP request to paged projection.
• Generic List Endpoint — the filter/search/order/page contract every generated CRUD list route exposes for free.

Diagrams

Every diagram on these pages is committed twice under diagrams/: the typed JSON IR it was authored from, and the rendered .svg the Markdown embeds. Edit the IR, re-render, and commit both — never hand-edit the SVG.

Diagram	Shows	Referenced from
templates-solution-layers	Project layers and which way the references point	root README.md, DDD guide
templates-request-pipeline	Every stage a request crosses, and each short-circuit response	root README.md, API pipeline
templates-domain-event-path	An event from aggregate to handler, across the save boundary	EF Core domain events
templates-crud-generation	Attributes in, generated requests/handlers/routes out	CRUD attributes
templates-aspire-topology	What the Aspire host provisions and injects	Template features

How the plumbing works

• API Request Pipeline — what happens to a request before it reaches a handler.
• SlimMessageBus Messaging — the command/query/event bus wiring.
• EF Core Domain Events — how domain events are collected and published.
• Auditing and Data Ownership — how audit fields get populated and can’t be forged.

Worked samples

• Manual vs. Automated — a layer-by-layer comparison of the two sample styles below.
• Manual sample: Purchase Orders — the full vertical slice written by hand.
• Automated sample: Products — creation and events declared by attribute.