dotnet-domain-primitives

Prevent primitive obsession in C# by replacing primitive types like Guid with strongly typed IDs. This enforces type-safe domain models, ensuring identifiers like OrderId are never accidentally mixed up with other Guids.

Value objects in .NET domain-driven design encapsulate meaningful primitives like EmailAddress with built-in validation and immutability. They enforce domain integrity by ensuring custom types carry validation rules directly within the domain model.

Handle boundary conversions for strongly typed IDs by ensuring conversions to and from primitive types occur only at explicit boundaries. This restricts serialization and persistence layers from corrupting domain model integrity.

Source generators are required to implement strongly typed IDs in C# efficiently. They automate the definition and usage of custom types for entity identifiers, reducing boilerplate while enforcing domain primitives.

The best way to enforce domain integrity with typed identifiers is automating custom type definitions for entity identifiers and meaningful primitives. This prevents accidental type mixing and pushes validation directly into the domain model.

Value objects in C# are used for persistence and transport layers through explicit boundary conversions. They maintain immutability within the domain while allowing necessary primitive type conversions strictly at serialization boundaries.