Class AmbiguousTimeException
Inheritance
Inherited Members
Namespace: NodaTime
Assembly: NodaTime.dll
Syntax
[Serializable]
public sealed class AmbiguousTimeException : ArgumentOutOfRangeException, _Exception, ISerializableRemarks
This occurs for transitions where the clock goes backward (usually by an hour). For example, suppose the time zone goes backward at 2am, so the second after 01:59:59 becomes 01:00:00. In that case, times such as 01:30:00 occur twice.
This exception is used to indicate such problems, as they're usually not the same as other ArgumentOutOfRangeException causes, such as entering "15" for a month number.
In theory this isn't calendar-specific; the local value will be ambiguous in this time zone regardless of the calendar used. However, this exception is always created in conjunction with a specific calendar, which leads to a more natural way of examining its information and constructing an error message.
Constructors
AmbiguousTimeException(ZonedDateTime, ZonedDateTime)
Declaration
public AmbiguousTimeException(ZonedDateTime earlierMapping, ZonedDateTime laterMapping)Parameters
| Type | Name | Description |
|---|---|---|
| ZonedDateTime | earlierMapping | The earlier possible mapping |
| ZonedDateTime | laterMapping | The later possible mapping |
Remarks
User code is unlikely to need to deliberately call this constructor except possibly for testing.
The two mappings must have the same local time and time zone.
Properties
EarlierMapping
Declaration
public ZonedDateTime EarlierMapping { get; }Property Value
| Type | Description |
|---|---|
| ZonedDateTime |
Remarks
This occurs for transitions where the clock goes backward (usually by an hour). For example, suppose the time zone goes backward at 2am, so the second after 01:59:59 becomes 01:00:00. In that case, times such as 01:30:00 occur twice.
This exception is used to indicate such problems, as they're usually not the same as other ArgumentOutOfRangeException causes, such as entering "15" for a month number.
In theory this isn't calendar-specific; the local value will be ambiguous in this time zone regardless of the calendar used. However, this exception is always created in conjunction with a specific calendar, which leads to a more natural way of examining its information and constructing an error message.
LaterMapping
Declaration
public ZonedDateTime LaterMapping { get; }Property Value
| Type | Description |
|---|---|
| ZonedDateTime |
Remarks
This occurs for transitions where the clock goes backward (usually by an hour). For example, suppose the time zone goes backward at 2am, so the second after 01:59:59 becomes 01:00:00. In that case, times such as 01:30:00 occur twice.
This exception is used to indicate such problems, as they're usually not the same as other ArgumentOutOfRangeException causes, such as entering "15" for a month number.
In theory this isn't calendar-specific; the local value will be ambiguous in this time zone regardless of the calendar used. However, this exception is always created in conjunction with a specific calendar, which leads to a more natural way of examining its information and constructing an error message.
Zone
Declaration
public DateTimeZone Zone { get; }Property Value
| Type | Description |
|---|---|
| DateTimeZone |
Remarks
This occurs for transitions where the clock goes backward (usually by an hour). For example, suppose the time zone goes backward at 2am, so the second after 01:59:59 becomes 01:00:00. In that case, times such as 01:30:00 occur twice.
This exception is used to indicate such problems, as they're usually not the same as other ArgumentOutOfRangeException causes, such as entering "15" for a month number.
In theory this isn't calendar-specific; the local value will be ambiguous in this time zone regardless of the calendar used. However, this exception is always created in conjunction with a specific calendar, which leads to a more natural way of examining its information and constructing an error message.