TimeZoneOffset Not Working Properly

[Marc]

2010.3.1109.40

I created a non recurring appointment on March 1 2011 with a start date and time of March 16 2011 at 11am.  After it was created it showed in the scheduler correctly as11am.  However, now that March 16th has come the appointment is shown in the scheduler as starting at noon (1hr ahead of what its suppose to start on).  In the database its stored as "2011-03-15 19:00:00.000", my server time zone is PST (Pacific Standard Time).  I have created my scheduler and data access as outlined here and have a load event as shown below.  Please advise on how to get my events to show properly, its much more than just this event and this is a problem in production right now. 

protected void RadScheduler1_Load(object sender, EventArgs e)
{
    TimeZone localZone = TimeZone.CurrentTimeZone;
    TimeSpan currentOffset = localZone.GetUtcOffset(DateTime.Today);
    this.RadScheduler1.TimeZoneOffset = currentOffset;
}

[Nikolay Tsenkov]

Hello Marc,

The problem you experience is caused by the fact that the Scheduler does not keep any additional time zone information (the TimeZone in which an appointment is scheduled).
In your case the TimeZone has changed (due to Daylight Saving Time) and the appointment is displayed according to the new TimeZone.

This is something we are going to research on implementing in future development of the control.


Kind regards,
Nikolay Tsenkov
the Telerik team

[Vladimir]

I also have a problem with daylight savings time.
If I create an event for March 30, 13:00 (GMT+1), it is stored in DB in UTC as March 30 11:00 UTC - it is correct because it is DST
but it is displayed at March 30, 12:00 in scheduler now (February 15), because TimeZoneOffset is GMT+1

Does the control support processing DST correctly now ? Or can you advice other way to show events properly ?

[Peter]

Hi Vladimir,

Thank you for reporting this issue. I have logged it and our developers have already began working on it. We will let you know when we fix it.

Greetings,
Peter
the Telerik team

[Ken]

Any update on this issue?

[Peter]

Hi Ken,

Thank you for your inquiry. The issue is still present, but we are currently working on resolving it.

Peter
the Telerik team