Use this page when deciding which TOON package belongs in which project.
DevOp.Toondotnet add package DevOp.Toon
This package depends on DevOp.Toon.Core and brings the runtime surface with it.
Choose DevOp.Toon.Core when a project only needs compile-time TOON contracts, for example:
ToonPropertyNameAttributeToonDelimiterToonKeyFoldingToonPathExpansionToonObjectArrayLayoutThis is the right choice for shared DTO libraries that should not take a dependency on serialization behavior.
Choose DevOp.Toon when a project needs runtime behavior:
ToonEncoderToonDecoderToonService and IToonServiceAddToon(...)Use DevOp.Toon.API when TOON should participate in ASP.NET Core MVC request and response handling on the server side.
Use DevOp.Toon.Client when a project needs to call a TOON-first API — automatic TOON encoding of request bodies, TOON/JSON response negotiation, and DI registration via AddToonClient(...).
Use DevOp.Toon in:
Use DevOp.Toon.Core in:
In larger solutions, keep DevOp.Toon.Core in the model layer, DevOp.Toon at application boundaries where serialization happens, DevOp.Toon.API at the server API edge, and DevOp.Toon.Client in projects that call TOON-first APIs.