Central Package Management (CPM) and AllowedVersions in <PackageVersion>

[christophwille]

The basic idea

<PackageVersion Include="FluentAssertions" Version="7.0.0" AllowedVersions="[7.0.0,8.0.0)" />

with a syntax like https://learn.microsoft.com/en-us/nuget/concepts/package-versioning?tabs=semver20sort#version-ranges

Can this be done? (and is there anyone else who has a similar problem to solve)

[christophwille]

Actually... AllowedVersions isn't needed as I just found out, locking to a specific version works like this:

<PackageVersion Include="FluentAssertions" Version="[7.0.0]" />

What I haven't figured out is the above "anything lower than 8"

[jeffkl]

The syntax for a version lower than something is (,1.0), so this should have the desired result:

<PackageVersion Include="FluentAssertions" Version="(,8.0)" />

[christophwille]

I could somewhat make it work with Version="(7.0,8.0)" (without a lower bound, it would pick 1.3.0.1)

However, main issue still is that Manage NuGet Packages in VS still recommends me to upgrade to beyond 8.0 (8.2 at the time of writing) even with the variant of Version.

[jbennink]

@christophwille I used it on Mediatr Version="[12.5.0,13.0.0) and that did not show the update to 13.0.0 (currently). When I change it to `Version=[12.5.0,13.0.1)" it does show me the 13.0.0 update. Perhaps a VS2022 update was needed.

[jbennink]

So to be clear, the "allowedVersions" attribute is not supported in CPM? You should restrict versions in the Version directly with the same syntax as previously available in the allowedVersions tag?

As @christophwille stated, how does the build determine which version to use when you just give it a range. My guess would be that it will always choose the highest available on nuget inside the bounds, but then how can I see which version that is outside of VS. Using a Version attribute to denote the current version and the "alowedVerions" to restrict the bounds feels much cleaner!