I fixed two major problems concerning the handling of DateTime64 data:
Unix timezones from the server, e.g. 'Europe/Berlin' couldn't be converted to Windows timezones like 'W. European Standard Time' when using a Windows client
The time of DateTimeOffset objects before 01-01-1970 was shifted due to wrong DST calculations and the timezone offset was wrong, too. I couldn't get this to work correctly with standard .NET functions, so I integrated the NodaTime library for this.
The problem is, that the Windows timezone database does not have historical data, only data enough to cover practical "current" times (and Windows wasn't around in 1972). The timezones with DST have no dynamic adjustment rules. Noda Time does include the necessary historic data.
Note: I removed support for netcoreapp3.1 and net6.0, because I didn't want to install these legacy frameworks on my PC. Don't merge the respective line in the .csproj file, if you still want to support them.
I fixed two major problems concerning the handling of DateTime64 data:
Note: I removed support for netcoreapp3.1 and net6.0, because I didn't want to install these legacy frameworks on my PC. Don't merge the respective line in the .csproj file, if you still want to support them.