Nuget Package - feed (VSTS) :Exception 'System.AggregateException' thrown when trying to add source
Solution 1
I met this issue today and fix it by following:
If you have delete the feed from VSTS, then you need to delete it from VS\Tools\Options\Nuget Package Manager\Package Sources:
If you didn't delete the feed in VSTS and want to use it, sign in with your VSTS team project account from VS upper right corner and restart VS:
Solution 2
This is may be an addition to the actual answer. I had to disable the check boxes as shown in below image to get the issue resolved. I think it might help to someone.
Solution 3
I had the same issue and I fixed issue by disabling my custom NuGet servers. Go to Tools->Options->Nuget Package Manager and disable your custom NuGet servers
Solution 4
Since this is the first Page I hit with my Problem:
If you get the error for nuget.org site, increase Version number:
https://api.nuget.org/v3/index.json -> https://api.nuget.org/v4/index.json
under Tools->Options->Nuget Package Manager (see Image from @Eddie-MSFT)
V3 doesn't seem to work since today.
Related videos on Youtube
Hussein Salman
Engineering Manager & Cloud-Native Architect, focusing on Kubernetes, Containers & Microservices. Check out my youtube channel: https://www.youtube.com/channel/UCoAh8g6dmwXQUwKhkggUFIA
Updated on July 09, 2022Comments
-
Hussein Salman almost 2 years
I have created a new feed with in Package Release hub (VSTS), installed the credentials, then added the package source.
Now, I am using Visual Studio 2015 to install Micrososft.Aspnet.mvc to a project, however it gives the following error:
Exception 'System.AggregateException' thrown when trying to add source 'https://mysite.pkgs.visualstudio.com/DefaultCollection/_packaging/MyLogUtils/nuget/v3/index.json'. Please verify all your online package sources are available.
I need to install NuGet packages normally, so I removed the feed from VSTS. However, the problem persists. How can this problem be resolved?
-
Eddie Chen - MSFT about 8 yearsWhat's the detailed Visual Studio version you use? Nuget Package Manager works with VS2015 Update1 and later. Does it still occur if you delete the new added source from your PC? And can you share the detailed steps to reproduce this issue?
-
Eddie Chen - MSFT about 8 yearsA reference for you: github.com/NuGet/Home/issues/2598
-
-
Joel Tipke almost 8 yearsDelete all other feeds except the first nuget and that resolved the issue for me.
-
Dan Leksell over 6 yearsThis helped me. I had an out dated package sources in my package sources that didn't exist anymore. Even though I was trying to update a package from a different source it seemed to still fail because it was presumably trying to connect to one of the old non-existing sources. Thanks!
-
CJBS about 6 yearsI had a custom NuGet package source and was getting the timeout error. Per this answer, I disabled the custom source, closed this dialog, refreshed the list of packages, then re-opened the package sources dialog and re-enabled my package source. Then, after refreshing my packages, installation of custom NuGet packages was again possible.
-
AHAMED AAQIB over 4 yearsIt's help to avoid download same package to each user in a team.There for share package source available.