Revisiting the V3 Nuget URL question

Recently started digging into jetbrains rider, and it seems as if it possibly supports only the nuget v3 urls. Proget at least formerly only supported v2 urls, leaving us at a bit of an impass when it comes to letting our engineers build code with jetbrains rider.

I'm curious if any of the v3 url stuff has been publicizied or there are any plans on supporting the v3 urls in the near future. While I think jetbrains should just support v2 urls, it does feel a bit bad asking them to, when nuget v3 has been around and mostly everything supports it now.

Thanks!

Product: ProGet
Version: 4.8.0

Just to be clear, ProGet and other tools support NuGet v3.x and v4.x clients.

The confusing part is this concept of the so-called "V3-API" that is used by a client and server to communicate. This API is private, which means it is unsupported, undocumented, and is intended to be used exclusively between the official NuGet client and NuGet.org.

Will Microsoft make it public? That's obviously a better question for Microsoft. But as of our last conversations with the NuGet team, it is no longer on their roadmap over the next few years.

You should most definitely JetBrains know this, and encourage them to support the public API; given the early state of Rider, they are certainly focusing on finding their market and early users, and your feedback will go a long ways. If they intend to be a product used by enterprises, they will need to support private enteprrise repositories like ProGet.

We do not have any contacts on that team, but even if we did... coming from a user of theirs is much more valuable than another ISV.

Hi Alana,

It isn't clear for me how to setup my proget to use https://api.nuget.org/v3

Should "https://api.nuget.org/v3" be the connector url?

Besides that, is there any tutorial to setup ProGet with https://api.nuget.org/v3?

You cannot use that URL to connect with ProGet; it is not a public API, and it is only intended for use by Microsoft-owned products, such as nuget.exe and Visual Studio.

please use www.nuget.org/api/v2

They've started documenting the API now over at

https://docs.microsoft.com/en-us/nuget/api/overview

INdeed; actually, we've updated our documentation on this matter -- and we do have supporting the v3 api on our roadmap now that it's supported by Microsoft.