Support for NuGet v3

NuGet V3 is out with VS2015.

There are packages that actually require the dependency management improvements of NuGet V3. See the package System.Collections 4.0.10 hosted on Nuget.org. It specifically says it needs NuGet 3.0 to use.

This package cannot be mirrored to Proget and so we are now at a point where Proget becomes an obstacle, rather than a huge help. Using Proget to attempt resolve the dependency fails. Using the nuget.org feed succeeds.

If there is some additional setup for Proget that makes this work, please let me know,

Product: ProGet
Version: 3.7.5

Unfortunately, v3 is still a work-in-progress; the API is entirely different, and it's not yet documented/stable yet; there's also no [https://docs.nuget.org/consume/installing-nuget#command-line-utility](v3 command-line tool) yet, which makes it difficult/unusable on build machines. We expect v3 to stabilize in the coming months, as the team ships more versions. In the mean time, we can't really reverse-engineer a moving API.

That being said, the v3 client is backwards compatible. I'm able to view the package and download as per normal via ProGet. I didn't test in a ASPNET5 (beta) project however.

If you're seeing errors using the v2 api endpoint, then that sounds like a bug in either the client or proget; please use fiddler to see exactly what requests are being issued, and then share those; it may be a simple fix with resolving/searching all the new framework monikers.

For what it's worth, there is now a command-line NuGet v3.1 client at http://dist.nuget.org/win-x86-commandline/v.3.1.0-beta/nuget.exe. See the NuGet 3.1 release notes.

ygeelen-tb

ProGet still doesn't seem to support connectors for https://api.nuget.org/v3/index.json ? When can we expect support for this?

We don't have any ETA for supporting v3, as the v2 API is fully compatible. Currently, only the NuGet client tools use the v3 API, so there is no real need to support yet as we see it.

We will work with the NuGet team if any of the compatability changes to start supporting it.

Any update on this? We would like to start using semver 2 on our packages.

Well, the NuGet API version is totally unrelated; and regarding the v3 API, it's still not stable/public yet, but they are planning a stable/public API at some point in the future (no ETA).

Regarding SemVer v2 support for NuGet packages/feeds, tut The NuGet team reports they may support it in v3.5 or v3.6; if/when that happens, we'll add support for it in ProGet's NuGet feed.