New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package manager UI: Doesn't display new version after updating a package #3041

Closed
spadapet opened this Issue Jun 24, 2016 · 1 comment

Comments

Projects
None yet
3 participants
@spadapet

spadapet commented Jun 24, 2016

This repro is the same as: #2976
Similar to: #2828

But now with the latest dotnet tooling, the package restore does happen after updating a package version. So there is no broken functionality. It's just the package manager UI that doesn't update the display of what version is installed.

Repro steps:

  • Create .NET Core Class Library project in VS
  • Open NuGet package manager (right click project node | manage nuget packages)
  • Install CsvHelper 2.14.3 package from nuget.org
  • Go to Installed tab, and hit Update to update to 2.15.0

Result:

  • The installed version display still shows the old version (2.14.3) and should show 2.15.0

Note:

  • Switching away from the tab and going back will update the displayed version
@rohit21agrawal

This comment has been minimized.

Show comment
Hide comment
@rohit21agrawal

rohit21agrawal Jun 24, 2016

Contributor

@spadapet What version of dotnet tooling are you using with this? I have an older version which still repros the bugs you linked to.

Contributor

rohit21agrawal commented Jun 24, 2016

@spadapet What version of dotnet tooling are you using with this? I have an older version which still repros the bugs you linked to.

rohit21agrawal added a commit to NuGet/NuGet.Client that referenced this issue Jun 29, 2016

fix update ui issue for net core projects where detailcontrol install…
…ed version does not show right version after updating package (#719)

Fixes issue : NuGet/Home#3041

fix update ui issue for net core projects where detailcontrol installed version does not show right version (in the installedversion textbox) after updating a package

this is because for netcore projects we do not get notified when a package update is complete, so by the time the json file is updated with the new version, we have already updated the UI with the older version.

the fix basically involves picking up the right version from the packageitemlistviewmodel instead of relying on the json file .

rohit21agrawal added a commit to NuGet/NuGet.Client that referenced this issue Jun 29, 2016

fix update ui issue for net core projects where detailcontrol install…
…ed version does not show right version after updating package (#719)

Fixes issue : NuGet/Home#3041

fix update ui issue for net core projects where detailcontrol installed version does not show right version (in the installedversion textbox) after updating a package

this is because for netcore projects we do not get notified when a package update is complete, so by the time the json file is updated with the new version, we have already updated the UI with the older version.

the fix basically involves picking up the right version from the packageitemlistviewmodel instead of relying on the json file .

rohit21agrawal added a commit to NuGet/NuGet.Client that referenced this issue Jun 29, 2016

fix update ui issue for net core projects where detailcontrol install…
…ed version does not show right version after updating package (#719)

Fixes issue : NuGet/Home#3041

fix update ui issue for net core projects where detailcontrol installed version does not show right version (in the installedversion textbox) after updating a package

this is because for netcore projects we do not get notified when a package update is complete, so by the time the json file is updated with the new version, we have already updated the UI with the older version.

the fix basically involves picking up the right version from the packageitemlistviewmodel instead of relying on the json file .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment