Home/ Questions/Q 80525
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T21:18:59+00:00

This problem occurred during daylight saving time change. After the change occurred, we’ve noticed

  • 0

This problem occurred during daylight saving time change. After the change occurred, we’ve noticed that our server application started writing into the log incorrect time – one hour ahead which means that .NET caches time zone offset. We had to restart our application to resolve this problem. I wrote a simple application to reproduce this problem. When I change the time zone while application is running, DateTime.Now property keeps producing the time in the old time zone. Does anybody know if there is a workaround for this problem apart from restarting the application?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Yes, the current time zone is cached. For a good reason, it avoids trouble with broken code that uses DateTime.Now to implement elapsed time measurement. Such code tends to suffer a heart-attack when the time suddenly changes by an hour or more.

    You will have to call System.Globalization.CultureInfo.ClearCachedData() to reset the cached value. The next call to DateTime.Now will now give the new local time. If you use the .NET 3.5 TimeZoneInfo class at all then you’ll also need to call its ClearCachedData() method. You can use the SystemEvents.TimeChanged event as a trigger.

    • 0