4

Fuck MS, why couldn't you update the NuGet API URL when NuGet updated? The warning on nuget.org states,

"This package will only be available to download with SemVer 2.0.0 compatible NuGet clients, such as Visual Studio 2017 (version 15.3) and above or NuGet client 4.3.0 and above"

It says nothing about using the V3 endpoint, so if you''re like me and updated NuGet to 4.5 and still got nothing but

"NU1101: Unable to find package Foo.Bar. No packages exist with this id in source(s): https://www.nuget.org/api/v2/"

...then you'll be very confused until it strikes you that there might be a new API version. Even if MS doesn't want to deprecate the V2 API just yet, it would be awfully nice to just state on the frickin' site that not only do you need NuGet >= 4.3.x, but also the correct feed URL.

$_DEITY knows how many dev-hours have been lost to this shit.

Comments
Add Comment