The Silverlight/WPF Scheduler controls include information about the time zone of the appointment. This is possible because they have access to the .NET 3.5-specific TimeZoneInfo class and they run on the client.
The same can't be easily applied to a server-side ASP.NET 2.0 control that also needs to support .NET 2.0. As a result the controls don't share export code and currently the ASP.NET Scheduler does not include time zone information in the exported file.
This can be remedied to some extent by exporting the appointments in UTC time and applying the needed correction as described in the KB article
that Nick mentions. In case your server is running in a different time zone, we can use the .NET 3.5 TimeZoneInfo class to obtain information for the desired zone:
TimeSpan aptStartOffset = TimeZone.CurrentTimeZone.GetUtcOffset(aptStart) - RadScheduler1.TimeZoneOffset;
TimeZoneInfo tz = TimeZoneInfo.FindSystemTimeZoneById(
"Eastern Standard Time"
TimeSpan aptStartOffset = tz.GetUtcOffset(aptStart) - RadScheduler1.TimeZoneOffset;
This isn't a perfect solution and we're planning to provide better time-zone support for RadScheduler. This will include time zone definition that will replace the current TimeZoneOffset property and will be used to properly format the exported file.
This is a significant change and such support will not be ready for Q1. We apologise for any inconvenience caused.
the Telerik team