Search

VS Nuget Package window shows wrong value for "Last Updated" date by Brian G

Active

1
0
Sign in
to vote
Type: Bug
ID: 773976
Opened: 12/10/2012 4:58:53 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
VS's window for managing Nuget packages doesn't show the correct time for when a package was last updated. I assume this time is the last time VS checked to see whether there was an update to a Nuget package, instead of the date at which the Nuget package was last updated. This should be fixed.

Also, the date seems to be shown in UTC time instead of local time. IE, the update time for every package is 12/11/2012 on my machine, but it's 12/10 today. If the time was a UTC time, then the date would be 12/11.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Go to Tools -> Library Package Manager -> Manage Nuget Packages for Solution.
Click on any of the Nuget packages in this list. Look at the "Last Updated" field on the right.
For me in the afternoon, the date shows up as 12/11/2012. It's about 5 PM on the 10th. So it seems that the date is shown in UTC time (I'm in the Redmond timezone, PST).

Product Language

English

Operating System

Windows 8

Operating System Language

Any

Actual results

Nuget packages appear to be updated based on today's date or tomorrow. This appears to be true for all nuget packages, regardless of when the package was last updated.

Expected results

1) Expected the Last Updated field to reflect when the package was updated.
2) Expected results to be shown in the right time zone - IE, there should be no way to see that a Nuget package was last updated tomorrow.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 12/10/2012 at 10:17 PM
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 Microsoft on 12/10/2012 at 5:51 PM
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)
Sign in to post a workaround.