Version range of packages are not supported

[ysethi92]

Steps to reproduce

• Create a project.
• Add a package.
• To the csproj file, specify a package dependency using interval notation for specifying version ranges. For example add:
  • <PackageReference Include="Moq" Version="[4.17.x,4.20.x)" />

Expected behavior

• Should complete the scan without any errors

Observed behavior

• Exception due to failure to parse the version range.
  • ArgumentException: '[4.17.x,4.20.x)' is not a valid version string.
    (Parameter 'value')
    at NuGetVersion Parse(string value)
    at ctor(string version)
    at PackageVersion Parse(string version) in PackageVersion.cs:34
    at ctor(string version) in PackageVersion.cs:10
    at PackageVersion ParseCurrentVersion(XElement element, string
    versionAttributeName) in XmlProjectFile.cs:47

[SteveDesmond-ca]

Thanks for this report.

Version 9.0.1 is currently in the process of being released, which will ignore version ranges so the scan can at least complete, since version ranges are valid from NuGet's perspective.

I've also added labels to this issue for potential future development to support determining the age of version-ranged dependencies.

[ysethi92]

Thanks for the update! That makes sense, glad that version 9.0.1 will at least allow scans to complete.

Looking forward to seeing future support for version-ranged dependencies when possible.