You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the comment at #1870 (comment) as well as browsing through the code, it looks like NuGet.PackageManagement is a good place to start exploring in order to replace code based on the v2 APIs with v3 APIs. However, it doesn't look possible to install NuGet.PackageManagement 3.4.3 right now (at least not without some sort of alternate package feed).
NuGet.PackageManagement 3.4.3 depends on
NuGet.Protocol.Core.v2 (>= 3.4.3) depends on
NuGet.Core (>= 2.11.1-rtm-812)
Unfortunately, the most recent NuGet.Core that's available on the gallery is 2.10.1. Where can NuGet.Core >= 2.11.1-rtm-812 be obtained, and why does the dependency chain for a primary NuGet library end up reaching into an alternate feed? I'm also a little confused as to why a v2 NuGet library is needed in the first place - I thought one of the goals of the NuGet v3 APIs was to leave the v2 libraries behind.
The text was updated successfully, but these errors were encountered:
Based on the comment at #1870 (comment) as well as browsing through the code, it looks like NuGet.PackageManagement is a good place to start exploring in order to replace code based on the v2 APIs with v3 APIs. However, it doesn't look possible to install NuGet.PackageManagement 3.4.3 right now (at least not without some sort of alternate package feed).
NuGet.PackageManagement 3.4.3 depends on
NuGet.Protocol.Core.v2 (>= 3.4.3) depends on
NuGet.Core (>= 2.11.1-rtm-812)
Unfortunately, the most recent NuGet.Core that's available on the gallery is 2.10.1. Where can NuGet.Core >= 2.11.1-rtm-812 be obtained, and why does the dependency chain for a primary NuGet library end up reaching into an alternate feed? I'm also a little confused as to why a v2 NuGet library is needed in the first place - I thought one of the goals of the NuGet v3 APIs was to leave the v2 libraries behind.
The text was updated successfully, but these errors were encountered: