On Thu, May 23, 2013 at 2:31 AM, Dominik Psenner <[email protected]> wrote:
> > I’m wondering, how often does your deployment computer travel from one > timezone to another while it is powered on? > Daily, but not in the way you think. The code runs on a device using Windows Embedded 7. The device is imaged at our site with OS and our code. Then it gets shipped to the customer site, connected to a network and fired up. Installer enters one identifying key and our backend server then configures the device over the network. We're trying to avoid a reboot after initial configuration if possible. I appreciate your recreation. Our system is indeed multi-threaded, and EACH of our threads has a handler that does the ClearCachedData() call. Time that our threads generate adjust appropriately. Log4net, as you discovered, does not. You're now at the point where I am - aware that the library doesn't seem to have a way to force this to change. If DOES change on a restart - we're trying to avoid that. It's an inconvenience. Not surprisingly, a lot of our initial support issues are related to installation and first start. The weird times make it awkward. So we do log that we changed the time and what the new offset is. I was just hoping this wasn't a new issue and someone more familiar with log4net would say "oh, that..." and forward a message from 2008 that had a magic incantation that would have the same effect as ClearCachedData(). Thanks for looking into this.
