• Introduction
• Overview
• Why does Noda Time exist?
• Installation
• Core
• Core concepts
• Choosing (and converting) between types
• Core types quick reference
• Recipes
• Design philosophy and conventions
• Migrating from 1.x to 2.0
• Text
• Text handling
• Patterns for Duration values
• Patterns for Offset values
• Patterns for Instant values
• Patterns for LocalTime values
• Patterns for LocalDate values
• Patterns for LocalDateTime values
• Patterns for OffsetDateTime values
• Patterns for ZonedDateTime values
• Patterns for Period values
• Patterns for OffsetDate values
• Patterns for OffsetTime values
• Patterns for AnnualDate values
• Advanced
• Date and time arithmetic
• Range of valid values
• BCL conversions
• Serialization
• Calendars
• Week years
• Threading
• Trivia
• Library
• Unit testing with Noda Time
• Updating the time zone database
• Mono support
• Limitations of Noda Time
• Current roadmap

Patterns for Instant values

The Instant type supports the following patterns:

Standard Patterns

The following standard pattern is supported:

• g: General format pattern. The ISO-8601 representation of this instant in UTC, using the pattern "uuuu-MM-ddTHH:mm:ss'Z'" and always using the invariant culture, with the default "start of time" and "end of time" labels. This is the default format pattern.

Custom Patterns

Instant supports all the LocalDateTime custom patterns. The pattern allows the culture to be specified, but always uses the ISO-8601 calendar, and always uses the UTC time zone. The "template value" is always the Unix epoch.