Home: PackageReference with a star in version is displayed under the updates tab/incorrectly represented in the installed tab

[emgarten]

Steps

1. File > New Project > NETCore console app
2. Add a package reference with a star
3. Open the NuGet UI and go to the installed tab
   

   Expected

No updates displayed, and the correct package info is shown

Actual

An update is displayed and no package info

    <PackageReference Include="Newtonsoft.Json">
      <Version>9.0.*</Version>
    </PackageReference>

Another customer report:
https://developercommunity.visualstudio.com/content/problem/277887/nuget-package-manager-doesnt-respect-package-refer.html

Another scenario: https://github.com/NuGet/Home/issues/3101

[SPEC]
https://github.com/NuGet/Home/wiki/%5BSpec%5D-NuGet-Build-Integrated-Project-handling-of-floating-versions-and-ranges-in-Visual-Studio-Client

[hkoelewijn]

It would be nice if VS allowed you to specify wildcards in the package manager in stead of us having to open the proj file directly

[pmiossec]

I think that's linked but when, in the "Package Manager Console", when you list the packages installed (with Get-Package command), you get the last number at "0".

Example:
For: <PackageReference Include="Newtonsoft.Json" Version="9.0.*" />
you will always get (even if 9.0.3 is really installed) : Newtonsoft.Json {9.0.0}

That's surely why "Nuget Package Manager` see it as "Should be updated"...

Is there some update on this issue? Seems to be postponed since v4.0... :cry:

[Neme12]

I found this after searching and trying out different things for 20 minutes thinking I must be doing something wrong with the wildcard :confused:

[tobiasschulz]

Yeah I really don't get why this has not been fixed yet.

[rfcdejong]

Any ETA?

[pmiossec]

That's the type of issue, that completely prevent the use of wildcard (I had to fallback to hardcoded version 😢 ) and so to put in place an update strategy that let me think that the paket ( https://github.com/fsprojects/Paket ) community driven project is a lot better solution to manage dependencies in a .net project....

That's a shame that the nuget team don't borrow most of the excellent ideas brought by this solution to spread them to the all the .net developers and make nuget a correct dependency manager 😢

[SaebAmini]

Wow, 3 years and no movement on such a basic package management feature?

[lengyeljanos]

really, we still can't use the floating version number along with visual studio?

[pmiossec]

I'm pretty sure that will be fixed soon, they put the 'priority:1' label... 😀😭

[Zastai]

Note: JetBrains' Rider IDE had the same issue (https://youtrack.jetbrains.com/issue/RIDER-37878). It was fixed the day after I reported it (the actual rollout won't be until the upcoming 2020.1 release though).

[PandeleFlorin]

2020 and STILL this is not fixed. Is it a major issue YES. Imagine a project that has multiple .sln files and you upgrade just some of the references in some of the slns but not all. Now I have to hunt for where the damn thing was used, in hundreds if not more slns.

[Duranom]

Can this be resolved soon? When is this getting planned? Any time at least before .NET 5 comes out?
It is causing for some battles between CI reporting packages out of date every now and then because someone keeps incidentally updating through the UI and forgetting to update the proper projects. Someone even raised the topic to reintroduce the nightmare Paket thing to tackle it.