Yes, this duplicated what was discussed already in this thread.
As I told there, you can rely (as a workaround) in implementing the DateChanged event on the own DateTimePicker instance.
In fact, that would make sense because you (typically) would want to get the date/time selected by the user… so receiving the DateTime in the event handler does it already.