Skip to main content

DevExpress v24.2 Update — Your Feedback Matters

Our What's New in v24.2 webpage includes product-specific surveys. Your response to our survey questions will help us measure product satisfaction for features released in this major update and help us refine our plans for our next major release.

Take the survey Not interested

SchedulerStorage.DateTimeSavingMode Property

Gets or sets in what time zone to store the appointment dates.

Namespace: DevExpress.Xpf.Scheduler

Assembly: DevExpress.Xpf.Scheduler.v24.2.dll

NuGet Package: DevExpress.Wpf.Scheduler

#Declaration

public DateTimeSavingMode DateTimeSavingMode { get; set; }

#Property Value

Type Description
DateTimeSavingMode

A DateTimeSavingMode enumeration member that specifies a conversion required before storing the DateTime value.

Available values:

Name Description
Appointment

Do not convert Start and End appointment values before storing them in the data source.

Storage

Convert Start and End appointment values to the time zone of the SchedulerControl before storing them in the data source.

Utc

Convert Start and End appointment values to UTC before storing them in the data source.

#Remarks

Important

You are viewing documentation for the legacy WPF Scheduler control. If you’re starting a new project, we strongly recommend that you use a new control declared in the DevExpress.Xpf.Scheduling namespace. If you decide to upgrade an existing project in order to switch to the updated scheduler control, see the Migration Guidelines document.

If for any reason (e.g. to simplify queries for DateTime values stored in the data source) you require that the appointment start and end data belong to the same time zone, set the DateTimeSavingMode to the DateTimeSavingMode.Storage value to store them in the timezone of the storage (specified using the SchedulerStorage.TimeZoneId property).

Tip

Use the UTC time zone for the storage and set the DateTimeSavingMode to the DateTimeSavingMode.Storage value in your applications to make the DateTime data consistent throughout different databases used in your applications.

See Also