NET Framework System.TimeZoneInfo class to specify its time zone and, as a result, will always use Microsoft Time Zone Index Values.īefore allowing end-user modification of appointment time zones, be sure to establish mappings for appointments and resources.ĭaylight saving time (DST) is a region-specific practice of setting clocks one hour ahead of standard time for a period of the year to make better use of natural daylight. In this case, the application will dynamically adjust for the time zone of the host environment (e.g., Korea Standard Time), and DateTimes will be displayed properly. For example, if the appointment data is with respect to EST (Eastern Standard Time) and the application is run from a region in KST (Korean Standard Time), the SchedulerStorageBase.TimeZoneId can be set to “Eastern Standard Time” while the SchedulerOptionsBehaviorBase.ClientTimeZoneId remains. To account for varied time zones among end-users, set the scheduler storage TimeZoneId to an appropriate value for the source data and set the ClientTimeZoneId for the client’s local time. This may lead to a mismatch among end-users from different time zones referencing the same appointments. By default, both properties are set to the time zone of the host system (i.e., ). SchedulerControl displays these stored appointments in its own SchedulerOptionsBehaviorBase.ClientTimeZoneId. The SchedulerStorageBase.TimeZoneId property is the associated time zone for the stored appointments. The topic consists of the following sections.Īppointment data is saved in a scheduler storage object. This article explains how the control calculates these time spans for both regular and ‘floating’ appointments. The Scheduler Control can recalculate appointment start and end time depending on the currently used time zone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |