Closed zwillikon closed 1 month ago
There is probably some nuget configuration somewhere that's referring to those old folders - I assume at some point they were added as extra package sources
You could look for a nuget.config
file under the ~/.nuget
folder and see if you can edit out those old references. Or, dotnet new nugetconfig
would generate you a fresh default configuration file
I've never used nuget.
https://github.com/OSGeo/gdal/tree/master/swig/csharp is the perpetrator – dotnet new nugetconfig
didn't reset that.
I'm not really sure what else to suggest, other than just wiping your ~/.nuget
folder entirely?
It looks like dotnet new nugetconfig
just generates a new nuget.config
file in your current directory, so you'd have to move that to replace the one under your ~/.nuget folder
@cameronwhite I don't have nuget (or pip, conda, conan, ...) installed.
I'm sorry for my ignorance: .NET always includes some NuGet e.g. at /usr/share/dotnet/sdk/8.0.108/NuGet.Configuration.dll
Sorry yeah, I should have clarified that dotnet is using nuget internally for packages
When I build Pinta
/usr/bin/dotnet publish Pinta.sln --configuration Release -p:BuildTranslations=true -maxcpucount:1 --self-contained false -p:PublishDir=./pinta/src/Pinta/publish
my .NET SDK wants to restore an old private project of mine:
This is obviously out of your domain – I would be nevertheless glad for an answer. How do I direct dotnet to give up on and delete those old builds?