Fixes #525. Resolving a package, when there is both an unversioned and (many) versioned candidates no longer fails with a null dereference. I believe this is a rare situation - usually all candidates for a package will be versioned when there is more than one.

Author: markfinal

Bam.Core/Package/PackageDefinition.cs

@@ -1099,7 +1099,8 @@ public static void
                 var candidates = candidatePackageDefinitions.Where(item => item.Name.Equals(depName, System.StringComparison.Ordinal));
                 if (depVersion != null)
                 {
-                    candidates = candidates.Where(item => item.Version.Equals(depVersion, System.StringComparison.Ordinal));
+                    // the item.Version check is in case the candidates list has both versioned and an unversioned package
+                    candidates = candidates.Where(item => item.Version != null && item.Version.Equals(depVersion, System.StringComparison.Ordinal));
                 }
                 var candidateCount = candidates.Count();
                 if (0 == candidateCount)

Changelog.txt

@@ -1,3 +1,5 @@
+09-Mar-2019 Fixes #525. Resolving a package, when there is both an unversioned and (many) versioned candidates no longer fails with a null dereference. I believe this is a rare situation - usually all candidates for a package will be versioned when there is more than one.
+
 09-Mar-2019 Fixes #524. Upgraded NuGet dependencies:
  GitInfo from 2.0.15 to 2.0.20
  Microsoft.NET.Test.Sdk from 15.8.0 to 16.0.1