Closed theonlychunsta closed 3 years ago
Thanks. I just added this to TimeZoneConverter 3.3.0, but I need to update TimeZoneNames for it as well.
Wow. glad I found this. So, when will 3.3.1 be out? :)
Also, perhaps as a future enhancement (after this fix goes out) if you could make a TryGetDisplayNameForTimeZone
so it won't crash this code I inherited.
I'll have an update for TimeZoneNames out soon. I'm working on it. The Windows display names have to be re-built via TimeZoneWindowsResourceExtractor first. (It takes some time to get the VM with all the language packs installed and updated before extraction.)
Also, by its current design - GetDisplayNameForTimeZone
should have returned null
instead of throwing an exception. I'll fix that.
Not planning on adding TryGet*
methods to this library, at least not now.
Both are fixed in version 4.1.0. Thanks!
Good Job, I will grab it later today. Thank you.
A new timezone has been added by Windows in one of their recent updates, causing this exception to be thrown.