Inconsistent package version resolution with floating version ranges in NuGet restore
When a project declares a dependency using a floating version range (for example, [1.0,) ), the NuGet restore process may resolve different applicable versions on different machines or after clearing the local cache, even when the same package sources are configured. This behavior appears to depend on factors such as the order in which package sources are qu
nuget