TimeZoneInfo Conversions Incorrect

TimeZoneInfo Conversions Incorrect by XAECO

Active

Type:	Bug
ID:	780900
Opened:	3/7/2013 2:21:55 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I've been testing migrating my Reporting Services to SQL Reporting and during this realised the TimeZoneInfo class is unavailable. I set about creating my own TimeZoneInfo class and found during testing that the .Net TimeZoneInfo class is incorrect for some countries.

Details (expand)

Visual Studio 2012

Use the TimeZoneInfo class to convert the following dates and times across all countries to see the dates and times are converted incorrectly.

I have attached a sample website that converts a range of dates and shows the incorrect conversions.

English

Windows 7 SP1

English

TimeZoneName    Date Time    To UTC    TimeZoneInfo ToUTC    TimeZoneInfo back to Local
Ekaterinburg Standard Time    2/01/2008 22:00    2/01/2008 17:00    2/01/2008 16:00    2/01/2008 22:00
Fiji Standard Time    1/01/2009 0:00    31/12/2008 12:00    31/12/2008 12:00    1/01/2009 1:00
Jordan Standard Time    2/01/2008 22:00    2/01/2008 20:00    2/01/2008 19:00    2/01/2008 22:00
Kaliningrad Standard Time    2/01/2008 22:00    2/01/2008 20:00    2/01/2008 19:00    2/01/2008 22:00
Magadan Standard Time    2/01/2008 22:00    2/01/2008 11:00    2/01/2008 10:00    2/01/2008 22:00
Mauritius Standard Time    31/12/2008 23:00    31/12/2008 18:00    31/12/2008 19:00    31/12/2008 23:00
N. Central Asia Standard Time    2/01/2008 22:00    2/01/2008 16:00    2/01/2008 15:00    2/01/2008 22:00
Namibia Standard Time    2/01/2008 22:00    2/01/2008 20:00    2/01/2008 21:00    2/01/2008 22:00
North Asia East Standard Time    2/01/2008 22:00    2/01/2008 14:00    2/01/2008 13:00    2/01/2008 22:00
North Asia Standard Time    2/01/2008 22:00    2/01/2008 15:00    2/01/2008 14:00    2/01/2008 22:00
Russian Standard Time    2/01/2008 22:00    2/01/2008 19:00    2/01/2008 18:00    2/01/2008 22:00
Samoa Standard Time    2/01/2008 22:00    3/01/2008 9:00    2/01/2008 9:00    2/01/2008 22:00
Vladivostok Standard Time    2/01/2008 22:00    2/01/2008 12:00    2/01/2008 11:00    2/01/2008 22:00
W. Australia Standard Time    1/01/2009 1:00    31/12/2008 16:00    31/12/2008 16:00    1/01/2009 0:00
Yakutsk Standard Time    2/01/2008 22:00    2/01/2008 13:00    2/01/2008 12:00    2/01/2008 22:00

All other countries convert ok.

Expected converted dates to be identical when converted using the TimeZoneInfo class, my class or the website www.timeanddate.com

File Name	Submitted By	Submitted On	File Size
TZ.zip (restricted)	XAECO	3/14/2013	-

Posted by Microsoft on 3/22/2013 at 4:28 PM

Thanks for reporting this issue. It is valid issue and we are looking at fixing such issues in the future releases. Most of the issues here is because missing some of the historical data for some of the time zones.

Posted by Microsoft on 3/20/2013 at 2:11 AM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by XAECO on 3/19/2013 at 1:08 AM

I uploaded the attachment again as per your instructions. Thank you

Posted by Microsoft on 3/18/2013 at 12:22 AM

Hi XAECO,

Due to the server problem, would you please upload the file to the following workspace? Thank you for your time!

You can use the following workspace to upload the file:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=f75487e4-1650-4283-ba90-ea48cf824428
Password is WEXBO$l0qc66vw9b

Posted by XAECO on 3/14/2013 at 2:54 AM

I have attached a sample website which demonstrates the issue.

Posted by Microsoft on 3/11/2013 at 1:17 AM

Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team

Posted by Microsoft on 3/8/2013 at 10:52 AM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)