When the UltraCalendarInfo.LogicalDayOffset and UltraCalendarInfo.LogicalDayDuration properties are set to non-default values, the end developer is permitted to set the WorkDayEndTime property to a value that is earlier than that of the WorkDayStartTime property. This is so that a logical work day can be specified which spans across more than one day. For example, if the LogicalDayOffset property is set such that the logical day begins at 8PM on the previous day, setting the WorkDayStartTime property to 10PM and the WorkDayEndTime property to 4AM will result in a logical work day which begins at 10PM on the previous day and ends at 4AM on the current day.
Also note that setting the value of the WorkDayEndTime property to a value that is outside the range defined by the logical day properties will result in the value being forced to coincide with the end of the logical day.
Note: The date components of the WorkDayEndTime property are not applicable, as the property defines a time of day that is independent of any particular date.
The WorkDayEndTime and WorkDayStartTime properties, while not obsolete, have been enhanced by the addition of the WorkingHours collection property, which makes it possible to define multiple, discontiguous ranges of time as working hours. When the WorkingHours collection is populated, the WorkDayStartTime and WorkDayEndTime properties are not applicable.
Note: For a detailed explanation of the order of precedence used when resolving working hours and time slot appearances, refer to the IsWorkDay, WorkingHours, and TimeRangeAppearances properties of the OwnerTimeSlotSettings class.
Target Platforms: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012, Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2