Home: Version Range support in UI and PMC update

[zhili1208]

Hi everyone at NuGet.org.

I’m using new format of the nuget package management that is fully integrated with MSBuild, it is very awesome and work very good except that it have one really odd error.
In old format(packages.config), we could use allowedVersions to limit version of allowed nugets, in this new format Version range should specified in Version tag of the PackageReference but
we have 2 problems with this:
1) PackagaeManagerConsole does not respect this version limit,
So if I have Version=”[1.0.0, 1.5.0)” and there is a version 2.0.0 of the package, UI respect my limitation and show no update but Update-Package command will update my
reference to version 2.0.0
2) If package updated to a newer version(a version that is allowed in my range), then new version will be written in place of old version and it will remove my version range limit
So if I have Version=”[1.0.0, 1.5.0)” and there is version 1.1.0 and 2.0.0 of the package, and I use nuget UI, it will update my project to version 1.1.0 as expected, but as a
side effect it will change my Version tag to Version=”1.1.0” and so remove my version limitation, and now it will show that I have an update for version 2.0.0.

I want to know how I use this new format and use old good allowedVersions or something that have same effect.

[MattLavalleeMA]

Same here. Almost 2 years old for a P1??

[MagicAndre1981]

Any update on this issue? @nkolev92 @anangaur

We need to restrict the offered nuget updates similar to _allowedVersions_ in packages.config.

[Indigo744]

This issue is still open, even though it is really a showstopper when multiple people may update packages using the UI. Every time we need to step in and add back the constraints...

This is madness. PackageReference is supposed to be "the new norm" but clearly lacks of basic usability like this, which is known for almost 3 years... Come on!

[MagicAndre1981]

@donnie-msft when will this be fixed? In 16.9? Why don't we get any response from you @nkolev92 @anangaur?

I opened my solution and now get tons of .net 5 updates when I want to do updates from .net core 3.1.9 to 3.1.10

I now used my filemanager to search for 3.1.9 to list all csprojs and next used Search&Replace from notepad3 to update from 3.1.9. to 3.1.10 🤮