Is there a difference between instances of TimeZoneInfo for .NET 3.5 on Windows compared to Mono on OS X?

I am trying to call EWS (Exchange 2007 SP1) using Mono in OS X. I can connect to the service and authenticate, but any calls that I try to make result in an exception like this:

Microsoft.Exchange.WebServices.Data.ServiceResponseException was thrown "A time zone with the specified identifier was not found."

I tried to specify several different identifiers, and all of them lead to the same answer. I'm starting to wonder if TZI tags differ between platforms. If so, does anyone know how to resolve the differences?

+3
source share
1 answer

, . , :

    foreach (TimeZoneInfo tz in TimeZoneInfo.GetSystemTimeZones()){
                    Console.WriteLine("{0}, {1}, {2}, {3}", tz.Id,
                           tz.DisplayName, tz.StandardName, tz.DaylightName);

            }

CreateCustomTimeZone , Windows:

    TimeZoneInfo newtz = TimeZoneInfo.CreateCustomTimeZone("Central Standard Time",
               tzi.BaseUtcOffset, "(GMT-06:00) Central Time (US & Canada)", 
               "Central Standard Time");

. , ( , ..).

+5

All Articles