Replies: 3 comments 1 reply
-
The server side should be supported no problem (DateOnly is supported from .NET 6 actually). The client side requires us to support .NET Standard 2.0 because of Xamarin support, which does not include DateOnly. I'm looking at the appropriate point at which to drop Xamarin support and move the library to min .NET 6. At that point, I'll be able to support DateOnly and TimeOnly. There are no plans to support STS releases of .NET - I'm going to update the client and server to support .NET 8 when it reaches GA in November. |
Beta Was this translation helpful? Give feedback.
-
I've just used DateTime as the client hangs when calling Personally I need the .NET standard 2.0 as I'm part way through a project using Xamarin.Forms and don't really want to migrate to MAUI as I not had a good experience with it so far, it seems to still have a lot of niggles and workarounds, it's like the early Xamarin days all over again. |
Beta Was this translation helpful? Give feedback.
-
Will do once I get through my backlog. |
Beta Was this translation helpful? Give feedback.
-
I have a use case for DateOnly but I'm running into issue when syncing, I think its down to the de\serialization.
I can see that Newtonsoft JSON supports these from 13.0.2 and .NET from version 7
What does this lib use ? are there plans .NET 7
Beta Was this translation helpful? Give feedback.
All reactions