馃搶 _Transferred from https://github.com/aspnet/AspNetCore/issues/9680_
PackageReference exclusive definition does not work correctly.
_According to Microsoft Docs_
_Notation(1.0,2.0)Applied Rule1.0 < x < 2.0DescriptionExact range, exclusive_
dotnet --infodotnet new consoledotnet add package Ruya.AppDomainerror: Unable to find package Ruya.Primitives with version (> 1.0.470)
It should pick the correct version of the package _(Ruya.Primitives 1.0.487 in this case)_ correctly.

output of dotnet --info

Thanks for creating this @cilerler.
Do you know if this is a new behavior?
I'd imagine the problem is here, https://github.com/NuGet/NuGet.Client/blob/5b975f446808a318e0696c8c23cd2dd6b9aa817b/src/NuGet.Core/NuGet.Commands/RestoreCommand/SourceRepositoryDependencyProvider.cs#L211
Related https://github.com/NuGet/NuGet.Client/pull/2578.
I would imagine 2.2.10x line does not have this bug.
@rrelyea This looks like a regression worth investigating.
@nkolev92 as long as I know it was there forever.
Moreover, you are probably right about the code location; and, I don't see any indication of filtering the unlisted ones.
Quick check suggests that 2.1.500 does not have this bug, so I think my "educated guess" above is correct.
This is a regression.
Unlisted ones are handled in different ways depending on the scenario. Unlisted versions are allowed in certain cases.
Great, so, should I expect a fix soon? 馃槃
@cilerler
We will triage and come back to you when we know more.
As a workaround you can always specify
<PackageReference Include="Ruya.Primitives" Version="[1.0.471,)" />
It will have the same meaning.
@cilerler
This will be in:
5.1 of NuGet
16.1 of Visual Studio
2.2.300/ 2.1.700/ 3.0.100-preview6 of the SDK.
Most helpful comment
@cilerler
This will be in:
5.1 of NuGet
16.1 of Visual Studio
2.2.300/ 2.1.700/ 3.0.100-preview6 of the SDK.