Alex Martossy Ted Driver David Fowler Almost, it's local/UTC by default, depending if you used DateTime.Now or UtcNow.
Parsing a date time on the other hand sets it to Unspecified, which causes tons of errors everywhere around the globe.
Ted Driver David Fowler I believe Datetime has datetimekind unset by default which is interpreted as local time. But datetimeoffset without offset is utc.
Alex Martossy Ted Driver David Fowler It's mostly correct.
Internally DateTime is DateTimeKind.Unspecified and DateTime.Now is local time of the host machine.
When you return this date as a HTTP response, .NET5 or .NET6 started to interpret DateTimeKind.Unspecified as UTC.
Ted Driver The Long Dark People expessing frustration with a lack of communication until two weeks before the update to say they’re scrapping the whole roadmap and “it’s ready when it’s ready” are not trolls
TSKelso: Ted Driver Tom Johnson Sure—a month after they were notified the first time. This was the third time and a bit more public…
Ted Driver Chris Jones Same in Georgia/South Carolina, but the traffic was MUCH worse afterward than before.