Private Azure Devops Nuget | Source Linking | External Sources Error "NonAuthoritativeInformation" Click to Authenticate Follow
GIVEN: Visual Studio project has a private nuget package hosted on Azure Devops Artifacts with Source Linking configured properly
WHEN: Developer attempts to navigate to the implementation of a type/method contained in the nuget package
THEN: Resharper shows the following error: "External Sources: Cannot download <name of file>. NonAuthoritativeInformation (203). Click to authenticate"
Additional Information
If I go to Resharper Options > External Sources and select "Default Visual Studio navigation", I am able to successfully navigate to source code.
Please sign in to leave a comment.
Hello,
Sorry for the delay in responding.
Seems that Visual Studio is already authorized in the private repository, while ReSharper is not. Could you please enter the authorization information that ReSharper is asked for and check how it works for you.
Thank you.
Hi, when I fill out the form and click the test button, it says that the test is ok, but after clicking ok, nothing happens.
Hello Ievgen Pavlenko
Could you please provide some video demonstrating the issue? Also please start VS with the following command: ``devenv.exe /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose``, reproduce the issue and send us resharper_log.txt.
You can share the files via our upload service.
Hello Angelina Elycheva
Upload id: 2022_10_20_2v41SrESLfiMWJVVmjU5cU
thank you for the video.
Have you tried clicking on the notification that appears in the log and logging in there?
You can also try to enable `Decompile Methods` option in ReSharper | Options | Tools | External Sources to get decompiled code instead of Metadata View.
Thank you.
Hello Angelina Elycheva
Yes, I clicked on the notification. I don't know why the video recorder didn't record it.
When I click on the notification, a form opens. I fill out the form and click the test button; it says the test is OK. Then I click on the button, OK, but nothing happens
Could it be that the credentials are not correct? Have you tried connecting to the private source link directly from VS?
Thank you.