DatePicker - DateTimeOffset

[drei97]

Hello,

I am using the DatePicker control and wondering why this piece is dealing with DateTimeOffset.

Are there good reasons to do so? Why not a 'simple' DateTime? It seems that DateTimeOffset is rarely used in general, maybe because 99% of the coder do not know that this class exists and maybe 99,9% will never understand the difference between DateTimeOffset and DateTime?

Nevertheless, the difference doesn't matter for my application.

[msneijders]

Microsoft documentation seems to encourage the use of DateTimeOffset instead of DateTime:

These uses for DateTimeOffset values are much more common than those for DateTime values. As a result, consider DateTimeOffset as the default date and time type for application development.

This is possibly the reason its chosen for DatePicker.

[drei97]

Sorry, my post was somewhat misleading. I try again with different words.

I am using both controls DatePicker and DatePickerCalendar.

1. I would have expected that both are using class Date, since there is no possibility to enter a Time. But they doesn't. They are using a datatype which includes a Time. Why?

OK, if so

2. but why then one with DateTimeOffset and the other with DateTime?

Are there good reasons not to use Date? Are there good reasons not to use one single type for both?

For me, it is

1. not necessary to use a class with Time. It simply makes it more complex.
2. not consistent

So, I was wondering if I do not get the miracle behind that (design) decisions, or if there is no such concept and it is done without spending some thoughts about.

I was facing some issues since the data in my database have no time stamp, are simply of type Date. So I am a little bit annoyed about converting back and forth.

[msneijders]

Are there good reasons not to use Date?

That would be DateOnly I think. But that type did not exist when the control was first made probably.

but why then one with DateTimeOffset and the other with DateTime? -not consistent

You are probably right about that.

When I use avalonia controls in my apps, I often inherit my own controls from them. And then add for example a SelectedDateOnly property and let the control do the conversion, so I do not have to do that everywhere I use it, and I can use the type in my viewmodel what I want it to be. Might work for you too.

[drei97]

Are there good reasons not to use Date?

That would be DateOnly I think. But that type did not exist when the control was first made probably.

DateOnly was introduced with .NET 6.

When I use avalonia controls in my apps, I often inherit my own controls from them. And then add for example a SelectedDateOnly property and let the control do the conversion, so I do not have to do that everywhere I use it, and I can use the type in my viewmodel what I want it to be. Might work for you too.

It is worth a try.

thnx