dotnet-timezone

Resolve timezone questions for .NET and C# code with production-safe guidance and copy-paste-ready snippets. Identify the request type first: If the library is unclear, default to TimeZoneConverter for cross-platform work. If the scenario involves recurring schedules or strict DST rules, prefer NodaTime . If the user provides an address, city, region, country, or document containing place names: For each resolved location, provide: Then include a cross-platform snippet like: If multiple locations are present, include one block per location and then a combined multi-timezone snippet. If a location is ambiguous, list the possible timezone matches and ask the user to choose the correct one. Use references/timezone-index.md for Windows to IANA mappings. Always provide both formats: Use references/code-patterns.md and pick the smallest pattern that fits: Always include package guidance when recommending third-party libraries. Mention the relevant warning when applicable: For address and location requests: For code and architecture requests: Keep responses concise and code-first.