aspnetzero-dto-patterns

Place DTOs in the Application.Shared project under a feature-specific Dto folder. Create separate classes per operation: a ListDto inheriting EntityDto, an EditDto with validation attributes, a CreateDto, a GetForEdit output wrapper, and a paged input inheriting PagedAndSortedResultRequestDto.

ASP.NET Zero conventions use System.ComponentModel.DataAnnotations, not FluentValidation. Apply attributes like [Required], [StringLength(max)], [Range(min, max)], and [EmailAddress] directly on DTO properties, and avoid using double.MaxValue as a maximum.

GetForEdit takes NullableIdDto as input rather than a custom DTO. A null Id means create mode, returning a new DTO with defaults plus lookup data; a non-null Id loads the entity. UIs always call GetForEdit, even for create, to receive dropdown options.

No, the convention requires separate DTOs per operation. List DTOs inherit EntityDto with a non-nullable Id from the database, while Create DTOs carry only input fields with validation attributes. Mixing them breaks serialization and validation expectations.

Paged list inputs should inherit PagedAndSortedResultRequestDto, which provides paging and sorting parameters. Add a Filter string property as the standard name for text search across list queries.