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
The UI for Add Packages defers to the public nuget gallery even when that feed isn't in the packages.dependencies for the project in question:
You can see the fiddler logs in this image.
The two feeds for this project are private company feeds, one for internally-produced packages and one for specific approved versions of public packages, so in the ideal case I'd not see Paket.Core in the search results here.
I haven't looked into if the problem is the allowed source list that paket.core is using to do the lookup or if paket.visualstudio is at fault here.
The text was updated successfully, but these errors were encountered:
forki
added a commit
to fsprojects/Paket
that referenced
this issue
Jun 8, 2015
Awesome, we no longer see the public results, thanks!
We don't see any packages at all, but that's because our hosted Nuget server doesn't support the apiv3 autocomplete. It'd be nice to fallback to old-style search, but that's outside the scope of this issue.
The UI for Add Packages defers to the public nuget gallery even when that feed isn't in the packages.dependencies for the project in question:
You can see the fiddler logs in this image.
The two feeds for this project are private company feeds, one for internally-produced packages and one for specific approved versions of public packages, so in the ideal case I'd not see Paket.Core in the search results here.
I haven't looked into if the problem is the allowed source list that paket.core is using to do the lookup or if paket.visualstudio is at fault here.
The text was updated successfully, but these errors were encountered: