Concepts

These articles apply to either production stack (KZDev.SystemClock.PrimeTime or KZDev.PrimeTime). They focus on choosing between stacks, shared timer and DST behavior, and diagnostics.

Articles

• Choosing a package
• Schedule zone naming (why “Schedule” in API names?)
• Persistence and time conversions
• Timers, daylight saving, and testing
• Event monitoring (ETW)

Cross-track examples

Patterns that look the same on both stacks are gathered together (each page presents both side-by-side):

• Examples overview
• DI replacement with AddPrimeTestClock
• Test-clock control APIs

For stack-specific examples, see System Clock examples and PrimeTime (NodaTime) examples.