Gets the date when the adjustment rule ceases to be in effect.
Assembly: mscorlib (in mscorlib.dll)
The value of theproperty is a date value without a time component.
Because the end date of the current adjustment rule is typically not known, you can assign DateTime.MaxValue.Date to theproperty when you create a custom adjustment rule.
Unless there is a compelling reason to do otherwise, you should define the adjustment rule's end date to occur within the time interval during which the time zone observes standard time. Unless there is a compelling reason to do so, you should not define the adjustment rule's end date to occur within the time interval during which the time zone observes daylight saving time. For example, if a time zone's transition from daylight saving time occurs on the third Sunday of March and its transition to daylight saving time occurs on the first Sunday of October, the effective end date of the adjustment rule should not be December 31 of a particular year, since that date occurs within the period of daylight saving time.
By default, the registry in Windows XP defines a single adjustment rule whose end date is Friday, December 31, 9999 (the value of DateTime.MaxValue.Date), for each time zone. For time zones in the United States, the registry in Windows Vista defines two adjustment rules:
Monday, January 01, 0001, to Sunday, December 31, 2006.
Monday, January 01, 2007, to Friday, December 31, 9999.
This means that, although time zone adjustment rules stored in the registry are useful for performing current time zone-related operations, they cannot be reliably used for retrieving historical time zone information. For information about defining a custom time zone with multiple adjustment rules that can be used in a historical time zone-aware application, see How to: Create Time Zones with Adjustment Rules.
Available since 3.5