TCMProject.Infrastructure 26.5.22.1

• net10.0

  • Microsoft.EntityFrameworkCore (>= 10.0.0)
  • Microsoft.EntityFrameworkCore.Relational (>= 10.0.0)
  • System.Runtime.Caching (>= 10.0.0)
  • TCMProject.Common (>= 26.5.15.1)
  • TCMProject.DataSources (>= 26.5.15.1)
  • TCMProject.Utilities (>= 26.5.15.1)

UTC DateTime handling as the gold standard (Issue #3, timezone-standardization.md). TCMProject.Infrastructure adds fail-fast EF Core value converters (StrictUtcDateTimeConverter / StrictUtcNullableDateTimeConverter) and the ApplyUtcDateTimeConvention extension over ModelConfigurationBuilder: it forces every DateTime to Kind=Utc and rejects Kind=Unspecified on write instead of guessing a timezone. The existing lenient UtcDateTimeConverters are kept unchanged. TCMProject.Web adds System.Text.Json UtcDateTimeConverter/NullableUtcDateTimeConverter, a UtcDateTimeModelBinder + provider for query-string/route DateTime values, and the AddTcmUtcDateTime extension over IMvcBuilder to wire them in one call. Adoption is opt-in per service. TCMProject.DataSources: EntityFrameworkDataSourceConverter now throws BadRequestException (HTTP 400) instead of NullReferenceException (HTTP 500) when a DataSource sort or filter references a field that does not exist on the entity.