Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
ProGet Support of NuGet V3 Feed
-
I have ProGet 3.8.6 installed and working successfully with a NuGet feed. Our developers are using VS2013 and the feed URL is https://www.nuget.org/api/v2/
A new project is going to use VS2017 and it appears to want to use the feed URL https://api.nuget.org/v3/index.json
Does ProGet support using the NuGet feed URL https://api.nuget.org/v3/index.json?
If yes, then what do I need to do?
If no, then why not and when will it?Is there someone at Inedo I can talk to about this? Please provide a contact.
Product: ProGet
Version: 3.8.6 -
Neither of those are ProGet URLs, they are Microsoft's public NuGet package feed.
If you wish to connect Visual Studio to your ProGet instance, please see this tutorial on how to configure ProGet as a package source.
-
Alana,
You are correct. The ProGet URL we use is http://10.210.92.134:81/nuget/Default/
In ProGet it is associated with the Remote Repository with the URL https://www.nuget.org/api/v2/What I want to know is can I change the Remote Repository Connector URL to https://api.nuget.org/v3/index.json, or can I add another Connector with that URL?
I am trying to support using VS2017 with ProGet. Previously/currently we are only using VS2013.
Thanks.
-
I'm not sure if you can use the V3 url in a ProGet connector. I believe I've tried and it wouldn't' work. I defer to ProGet employee's to confirm that.
However, that won't affect your developers using VS 2017. They can connect to ProGet with the url that you provided earlier and they will see the same results. I have about 80 developers across VS 2013, VS 2015 and VS 2017 all using the same ProGet url, and all are working fine with the nuget.org connector in ProGet.
Please note, I do not work for ProGet. I'm a fellow customer offering assistance.
-
Hi,
Having the V3 API working would allow the access to Dotnet Core packages. Which seems not possible through V2 API.
Having Proget supporting this Api will be a plus since it is the default API since a while now. +1
Regards
-
Hi Sebastian,
You can access all of the DNC packages using the ODATA (v2) protocol API.
If you're finding an issue with it, it's totally unrelated to the API protocol. Please submit a different question with specific packages, reproduction steps and we can investigate
Cheers,
Alana
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login