TIME SCHEDULER TIME ZONES TRIAL

In this case during data binding RadScheduler assumes all dates to be UTC.If you use a custom provider or create the Appointment objects programmatically you should take care to convert the date-times to UTC by calling DateTime.ToUniversalTime() or by other appropriate means. If TimeZoneID property is not set the TimeZoneOffset property is applied. If it is set to 'True'all the appointments inherit the TimeZone of RadScheduler In order to allow selecting individual timezone for each Appointment in the Advanced Form the 'EnableCustomTimeZones' property can be set. The provider and the specific settings in each TimeZone are responsible for all DateTime related calculations. In addition to this a DataTimeZone field is added to enable eachAppointment to be set in different timezone.

If TimeZoneID is not set initially, the default time zone is (UTC). It uses TimeZoneInfoProvider capable of returning correct LocalToUTC and UTCToLocal information depending on the TimeZone RadScheduler should be operating under. To overcome these problems RadScheduler defines the TimeZoneID property. This places some additional overhead, but is essential for solving the following problems:ĭisplaying correct times for the appointments when the clients and/or the server are in different time zones.Ĭorrectly evaluating recurrence rules with respect to Daylight Saving Time. In order to properly handle time zones, RadScheduler uses the TimeZoneInfo object, which comes together with.

TIME SCHEDULER TIME ZONES TRIAL

Download free 30-day trial Handling Time Zones

Time scheduler time zones