Hi Morgan,
Okay, I think I'm beginning to understand the problem here. I'll need
to play with it a little to come up with the best fix, but I have a
workaround that should be good for the time being.
In your original crash stack, the error is coming from the static
constructor for OlsonUtil. As Zbigniew suspects, the offending line is
at the very bottom of OlsonUtil.cs:
OlsonUtil.GetTimeZone
(System.TimeZone.CurrentTimeZone.StandardName);
This is where the "Paris, Madrid" string is coming from. Apparently
different locales of Windows have different names for the timezones.
In other words, the timezone that comes in from the web request is
just fine; it's only the timezone that we're getting in this one line
which is wrong. We need to make a fix either to get a non-localized
timezone here, or use a version of TZ4Net that handles the localized
name.
Thus, you should be able to do a workaround just by hard-coding this
one line. In other words, please change this line to
OlsonUtil.GetTimeZone("Europe/Paris");
and see if that works! This is a smaller change than hard-coding
inside OlsonUtil.GetTimeZone itself. And I'll work on a real fix.
Please let me know if this works as a workaround. Thanks for putting
in so much work to track this down!
John