This is probably not a business reason. I do not think it is a coincidence that the value is exactly one year before DateTime.MaxValue
. DateTimePicker may have some internal logic that breaks pages into neighboring months that break near DateTime.MaxValue
, which did not cost a special case.
source share