如何使用凭据正确配置外部nuget包源？

Question

I have an external nuget package source in my project wich I added in Visual Studio 2017 by the Package Manager Settings . I can install the packages properly but when I click on publish (it´sa dotnet core console app). I get this error status:

2>Retrying 'FindPackagesByIdAsync' for source 'https://***.azure.com/*****/system.servicemodel.duplex/index.json'. 2>Response status code does not indicate success: 401 (Unauthorized).

I searched a solution which says to add the credentials using the cmd , but when I try to execute the command to add I get this error message from the cmd:

The name specified has already been added to the list of available package sources. Please provide a unique name.

So I need to remove the package source from the visual studio (using the Package Manager Settings) and after I remove the package source the cmd command works, but then I dont have access anymore to the external packages in Visual Studio (because I removed it to be possible to add from the command line).

How can I fix that?

EDIT: The cmd syntax is this:

nuget.exe sources add -name MyExternalSource -source https://***/nuget/v3/index.json -username nugetUser -password MyToken

Answer 1

It needs Identity when pushing or consuming packages through a Azure Devops feed.

I think you don't need to use command like nuget.exe sources Add -Name "TestNuget" -Source "https://xxx/nuget/v3/index.json" , since it is used to manage the package sources in Nuget.config file instead of solving the Unauthorized issue. See sources command .

I get this error status:

2>Retrying 'FindPackagesByIdAsync' for source 'https://***.azure.com/*****/system.servicemodel.duplex/index.json'. 2>Response status code does not indicate success: 401 (Unauthorized).

Most of the time, I met this kind of message when using Self-Contained deploy mode. But actually the publish can succeed in my machine with message like this:

(I think the publish also succeeds in your side, in this situation I think you can ignore it or publish the project the second time with same PublishProfile, the error message would go away)

Also you can publish the project with Framework-dependent mode after builds the project successfully.

If the publish failed:

1.And if your publish fails with that message, in my opinion you can remove the referenced packages by Nuget Package Manager UI , and remove the Feed Url from Package Sources UI .

2.Then restart VS and re-set the Feed Url in Package Sources Setting . No need to use command-line, use VS2017 UI and re-add the package after re-set the Package Source.

3.When you search the package from new-set feed like this , it will pop up an Identity Window which requires you to enter account and password, and then you're now authorized . After that you can find, consume the package in your project, and publish it successfully. Hope it helps.