Clever Geek Handbook

Proget Server Up but not available in Visual Studio

We reinstalled ProGet when we restored our server after discovering a security hole (not related to ProGet). The channel is displayed in the browser but is not available in Visual Studio.

When we restore our server, we have ProGet running on a temporary Azure server running and serving our NuGet packages. When comparing the two, one of the highlights is the API endpoint URL for the feed. For ProGet on Azure, this is an acceptable URL. enter image description here On ProGet, which we are trying to configure when we create our new server, it actually contains a password and the word "Default" (we have deprecated this password). enter image description here It doesn't seem right, but I don't think it can be changed. I tried reinstalling ProGet, but it kept my packages and feed.

How can I fix this so ProGet will serve Visual Studio? Thanks in advance.

+3


source to share


2 answers


This was fixed by clearing the value in the ODataBaseUrl in advanced settings. After that, the API endpoint URL changed to what it should - it's a fully qualified URL, not a strange string.



0


source


Which version of ProGet are you using?

If it's v3.7 or newer, the "Package Source URL" on the Browse Channels page is what you want to enter into Visual Studio:



ProGet Feed Overview Page

The "default" you see is just the feed name and there are no passwords in this url. The display hostname is just the name of the machine it is running on, so you can also use the DNS name or IP address if you are on Azure (for example, http: // {sitename} .cloudapp.net / nuget / { feedname})

+1


source






More articles:


All Articles