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!
An error occurred while communicating with the remote host. The error code is 0x80070016
-
Dear Indedo,
Allrecipes has a mirror of NuGet.org in our ProGet (4.6.7, build 2) instance. We’ve enabled the (nuget.org v3) feed connector for our mirror feed. Afterward, viewing the feed displays the following error message prominently:
There was an error with a connector: Data at the root level is invalid. Line 1, position 1.We see warning messages similar to the following for the feed In the ProGet error log:
An error occurred processing a GET request to http://INTERNALSERVERURL/nuget/nugetmirror/package/HtmlAgilityPack/1.4.6: An error occurred while communicating with the remote host. The error code is 0x80070016.Inedo frequently put off support for NuGet v3 support according to their forums. It’s Allrecipes understanding that this functionality is definitely now included and supported in ProGet.
We’ve had to disable internal ProGet usage for .NET Core applications every time a new .NET Core framework is released so our build agents can populate local NuGet caches. This takes a considerable amount of developer time.
Product: ProGet
Version: 4.6.7 -
Just to clarify... the "NuGet v3 API" is intended for internal-use (i.e. only nuget.exe and NuGet VS extension). Microsoft's new position is that they do not intend on making this API public or stable in the foreseeable future, and that they will continue to support the "NuGet v2 API" (which is documented and public) indefinitely. They actually use ProGet to test changes to v2 API.
That said, until this position changes, we will not reverse-engineer the v3 protocol. So this means you will need to use nuget.org/api/v2 in your connector, not the v3 url.
Both v2 and v3 API work with client tools, both support DotNetCore, etc. If you're finding a issues with DNC projects, then it's likely related to framework monikers or something like that. Please submit a ticket for this with specifics, so we can investigate and patch.
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