-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add DateIOnly/TimeOnly support to XmlSerializer and DataContractSerializer #56711
Comments
@eiriktsarpalis Is this one up for grabs? Not committing to anything yet, but I may have some time (and interest) for this. |
I defer to the area owners of serialization cc @StephenMolloy |
It seems, almost 2 years later, this hasn't picked up yet sadly |
Yes, I was very surprised to find this problem. 😯 |
Still failing in 7.0.306 Despite forcing new types like that XmlSerializer ser = new(typeof(MyClass), new Type[] { typeof(DateOnly), typeof(TimeOnly) });
I attach the code. Cheers |
…rc\System\Xml\Serialization\Types.cs" to separate namespace and files.
@Maximys I see a few related commits. Would you be willing to work on a pull request? |
Yes, @rgroenewoudt , I'll try to continue my work |
Is anyone actively working on this issue? If not, I'd be willing to consider getting involved. |
@eiriktsarpalis @StephenMolloy is there any plan to progress this? EF Core 8 now scaffolds I am unable to work around using |
This needs to be dealt with soon! Now that EF 8 is scaffolding DateOnly/TimeOnly properties, this is a big FAIL! |
Moving to Future as feature development for .NET 9 is now completed. |
Originally posted by @LaughingJohn in #51302 (comment)
The text was updated successfully, but these errors were encountered: