Incorrect conversion of the Appointment Start/End date when changing the TimeZone.

 

In this particular case, the control is bound to a custom object using SchedulerBindingSource. As demonstrated in the Binding to Business Objects help article. While using this set-up, deleting Recurrence does not delete the Exceptions collection in the business object. The exceptions collection property of the Appointment inside the RadScheduler is cleared, however, the changes are not transferred to the data object.

 

Appointments Start/End date is wrong when using different TimeZone for SystemTimeZone with DefaultTimeZone. Appointments are placed in the wrong date or the start/end properties are wrong in the EditAppointmentDialog.

AllDay event is rendered on two days when using different TimeZone for SystemTimeZone with DefaultTimeZone