Unable to find nuget local source error occurred while restoring nuget packages the local source doesn't exist

前端 未结 5 1106
说谎
说谎 2021-02-12 05:57

I\'ve been given a visual studio 2017 solution. When I open it fails as with the error:

Error occurred while restoring NuGet packages: The local source \'\\\\netw

5条回答
  •  天涯浪人
    2021-02-12 06:51

    Nothing of the proposed solutions above did it for me. And, honestly, I really don't like, what Microsoft is doing for some time now: each time there's another surprise when installing an update. :-(

    Analysis:

    Error occurred while restoring NuGet packages: The local source 'C:\Microsoft\Xamarin\NuGet' doesn't exist.
    

    Obviously NuGet is trying to restore from C:\\Microsoft\\Xamarin\\NuGet for s solution that has nothing to do with Xamarin. The solution compiled many times before and even getting it back from GIT did not change anything. So, the problem is not my solution. It is something more global.

    By the way: I DONT WANT TO USE THIS FOLDER, cause I don't use Xamarin!

    I found the following reference in the *.csproj.nuget.dgspec.json files in any obj folder of my solution. All these json files pointed to this Xamarin folder:

    "fallbackFolders": {
      "C:\\Microsoft\\Xamarin\\NuGet": {},  
      "C:\\Program Files (x86)\\Microsoft SDKs\\NuGetPackages\\": {},
      "https://api.nuget.org/v3/index.json": {}
    },
    

    Question: How does VS know about the fallbackFolders?

    I did not find any hint in any of my Visual Studio / NuGet configuration settings, as proposed above. I deleted all objfolder but each time when trying to compile or restore my packages, the reference came back.

    The SOLUTION for me was :

    • delete all objfolders in your solution (as mentioned above)

    • delete c:\Program Files (x86)\NuGet\Config\Xamarin.Offline.config

    There you will find the following:

    
        
    
    

    This file was introduced on my machine one week ago, and I think it came with the latest VS update (16.2). I did not go away with the latest update (16.2.1) from today.

提交回复
热议问题