Class Period

Represents a period of time expressed in human chronological terms: hours, days, weeks, months and so on.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Gets the number of days within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Returns whether or not this period contains any non-zero date-based properties (days or higher).

Type	Description
Int32	The number of days within this period.

Type	Description
Boolean	true if this period contains any non-zero date-based properties (days or higher); false otherwise.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Returns whether or not this period contains any non-zero-valued time-based properties (hours or lower).

Type	Description
Boolean	true if the period contains any non-zero-valued time-based properties (hours or lower); false otherwise.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Gets the number of hours within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Gets the number of milliseconds within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Gets the number of minutes within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Gets the number of months within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Gets the number of nanoseconds within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Type	Description
Int64	The number of hours within this period.

Type	Description
Int64	The number of milliseconds within this period.

Type	Description
Int64	The number of minutes within this period.

Type	Description
Int32	The number of months within this period.

Type	Description
Int64	The number of nanoseconds within this period.

Returns an equality comparer which compares periods by first normalizing them - so 24 hours is deemed equal to 1 day, and so on. Note that as per the Normalize() method, years and months are unchanged by normalization - so 12 months does not equal 1 year.

Type	Description
IEqualityComparer<Period>	An equality comparer which compares periods by first normalizing them. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Gets the number of seconds within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Gets the number of ticks within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Gets the number of weeks within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

Gets the number of years within this period.

This property returns zero both when the property has been explicitly set to zero and when the period does not contain this property.

A period containing only zero-valued properties.

Type	Description
Int64	The number of seconds within this period.

Type	Description
Int64	The number of ticks within this period.

Type	Description
Int32	The number of weeks within this period.

Type	Description
Int32	The number of years within this period.

Type	Description
Period	A period containing only zero-valued properties. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Returns the exact difference between two dates.

Type	Name	Description
LocalDate	start	Start date
LocalDate	end	End date

Type	Description
Period	The period between the two dates, using year, month and day units. (The value returned is never null.)

If end is before start, each property in the returned period will be negative.

Returns the period between a start and an end date, using only the given units.

Type	Name	Description
LocalDate	start	Start date
LocalDate	end	End date
PeriodUnits	units	Units to use for calculations

Type	Description
Period	The period between the given dates, using the given units. (The value returned is never null.)

If end is before start, each property in the returned period will be negative. If the given set of units cannot exactly reach the end point (e.g. finding the difference between 12th February and 15th March in months) the result will be such that adding it to start will give a value between start and end. In other words, any rounding is "towards start"; this is true whether the resulting period is negative or positive.

Returns the exact difference between two date/times.

Type	Condition
ArgumentException	`units` contains time units, is empty or contains unknown values.
ArgumentException	`start` and `end` use different calendars.

Type	Name	Description
LocalDateTime	start	Start date/time
LocalDateTime	end	End date/time

Type	Description
Period	The period between the two date and time values, using all units. (The value returned is never null.)

If end is before start, each property in the returned period will be negative.

Returns the period between a start and an end date/time, using only the given units.

Type	Name	Description
LocalDateTime	start	Start date/time
LocalDateTime	end	End date/time
PeriodUnits	units	Units to use for calculations

Type	Description
Period	The period between the given date/times, using the given units. (The value returned is never null.)

If end is before start, each property in the returned period will be negative. If the given set of units cannot exactly reach the end point (e.g. finding the difference between 1am and 3:15am in hours) the result will be such that adding it to start will give a value between start and end. In other words, any rounding is "towards start"; this is true whether the resulting period is negative or positive.

Returns the exact difference between two times.

Type	Condition
ArgumentException	`units` is empty or contained unknown values.
ArgumentException	`start` and `end` use different calendars.

Type	Name	Description
LocalTime	start	Start time
LocalTime	end	End time

Type	Description
Period	The period between the two times, using the time period units. (The value returned is never null.)

If end is before start, each property in the returned period will be negative.

Returns the period between a start and an end time, using only the given units.

Type	Name	Description
LocalTime	start	Start time
LocalTime	end	End time
PeriodUnits	units	Units to use for calculations

Type	Description
Period	The period between the given times, using the given units. (The value returned is never null.)

If end is before start, each property in the returned period will be negative. If the given set of units cannot exactly reach the end point (e.g. finding the difference between 3am and 4.30am in hours) the result will be such that adding it to start will give a value between start and end. In other words, any rounding is "towards start"; this is true whether the resulting period is negative or positive.

Type	Condition
ArgumentException	`units` contains date units, is empty or contains unknown values.
ArgumentException	`start` and `end` use different calendars.

Creates an IComparer<T> for periods, using the given "base" local date/time.

Type	Name	Description
LocalDateTime	baseDateTime	The base local date/time to use for comparisons.

Type	Description
IComparer<Period>	The new comparer. (The value returned is never null.)

Certain periods can't naturally be compared without more context - how "one month" compares to "30 days" depends on where you start. In order to compare two periods, the returned comparer effectively adds both periods to the "base" specified by baseDateTime and compares the results. In some cases this arithmetic isn't actually required - when two periods can be converted to durations, the comparer uses that conversion for efficiency.

Compares the given period for equality with this one.

Periods are equal if they contain the same values for the same properties. However, no normalization takes place, so "one hour" is not equal to "sixty minutes".

Type	Name	Description
Period	other	The period to compare this one with.

Type	Description
Boolean	True if this period has the same values for the same properties as the one specified.

Compares the given object for equality with this one, as per Equals(Period).

Type	Name	Description
Object	other	The value to compare this one with.

Type	Description
Boolean	true if the other object is a period equal to this one, consistent with Equals(Period)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of days.

Type	Name	Description
Int32	days	The number of days in the new period

Type	Description
Period	A period consisting of the given number of days. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of hours.

Type	Name	Description
Int64	hours	The number of hours in the new period

Type	Description
Period	A period consisting of the given number of hours. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of milliseconds.

Type	Name	Description
Int64	milliseconds	The number of milliseconds in the new period

Type	Description
Period	A period consisting of the given number of milliseconds. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of minutes.

Type	Name	Description
Int64	minutes	The number of minutes in the new period

Type	Description
Period	A period consisting of the given number of minutes. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of months.

Type	Name	Description
Int32	months	The number of months in the new period

Type	Description
Period	A period consisting of the given number of months. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of nanooseconds.

Type	Name	Description
Int64	nanoseconds	The number of nanoseconds in the new period

Type	Description
Period	A period consisting of the given number of nanoseconds. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of seconds.

Type	Name	Description
Int64	seconds	The number of seconds in the new period

Type	Description
Period	A period consisting of the given number of seconds. (The value returned is never null.)

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of ticks.

Type	Name	Description
Int64	ticks	The number of ticks in the new period

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of weeks.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Creates a period representing the specified number of years.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Returns the hash code for this period, consistent with Equals(Period).

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Returns a normalized version of this period, such that equivalent (but potentially non-equal) periods are changed to the same representation.

Months and years are unchanged (as they can vary in length), but weeks are multiplied by 7 and added to the Days property, and all time properties are normalized to their natural range. Subsecond values are normalized to millisecond and "nanosecond within millisecond" values. So for example, a period of 25 hours becomes a period of 1 day and 1 hour. A period of 1,500,750,000 nanoseconds becomes 1 second, 500 milliseconds and 750,000 nanoseconds. Aside from months and years, either all the properties end up positive, or they all end up negative. "Week" and "tick" units in the returned period are always 0.

Creates a PeriodBuilder from this instance. The new builder is populated with the values from this period, but is then detached from it: changes made to the builder are not reflected in this period.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

For periods that do not contain a non-zero number of years or months, returns a duration for this period assuming a standard 7-day week, 24-hour day, 60-minute hour etc.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Returns this string formatted according to the Roundtrip.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Adds two periods together, by simply adding the values for each property.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Subtracts one period from another, by simply subtracting each property value.

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Implementation of GetObjectData(SerializationInfo, StreamingContext).

A Period contains a set of properties such as Years, Months, and so on that return the number of each unit contained within this period. Note that these properties are not normalized in any way by default, and so a Period may contain values such as "2 hours and 90 minutes". The Normalize() method will convert equivalent periods into a standard representation.

Periods can contain negative units as well as positive units ("+2 hours, -43 minutes, +10 seconds"), but do not differentiate between properties that are zero and those that are absent (i.e. a period created as "10 years" and one created as "10 years, zero months" are equal periods; the Months property returns zero in both cases).

Period equality is implemented by comparing each property's values individually.

Periods operate on calendar-related types such as LocalDateTime whereas Duration operates on instants on the time line. (Note that although ZonedDateTime includes both concepts, it only supports duration-based arithmetic.)

Type	Condition
InvalidOperationException	The month or year property in the period is non-zero.
OverflowException	The period doesn't have years or months, but the calculation overflows the bounds of Duration. In some cases this may occur even though the theoretical result would be valid due to balancing positive and negative values, but for simplicity there is no attempt to work around this - in realistic periods, it shouldn't be a problem.

Type	Name	Description
Period	left	The first period to add
Period	right	The second period to add

Type	Name	Description
Period	minuend	The period to subtract the second operand from
Period	subtrahend	The period to subtract the first operand from

Type	Name	Description
SerializationInfo	info	The SerializationInfo to populate with data.
StreamingContext	context	The destination for this serialization.

Inheritance

Implements

Inherited Members

Namespace: NodaTime

Assembly: NodaTime.dll

Syntax

Remarks

Properties

Days

Declaration

Property Value

Remarks

HasDateComponent

Declaration

Property Value

Remarks

HasTimeComponent

Declaration

Property Value

Remarks

Hours

Declaration

Property Value

Remarks

Milliseconds

Declaration

Property Value

Remarks

Minutes

Declaration

Property Value

Remarks

Months

Declaration

Property Value

Remarks

Nanoseconds

Declaration

Property Value

Remarks

NormalizingEqualityComparer

Declaration

Property Value

Remarks

Seconds

Declaration

Property Value

Remarks

Ticks

Declaration

Property Value

Remarks

Weeks

Declaration

Property Value

Remarks

Years

Declaration

Property Value

Remarks

Zero

Declaration

Property Value

Remarks

Methods

Between(LocalDate, LocalDate)

Declaration

Parameters

Returns

Remarks

Between(LocalDate, LocalDate, PeriodUnits)

Declaration

Parameters

Returns

Remarks

Exceptions

Between(LocalDateTime, LocalDateTime)

Declaration

Parameters