Only uses nuget.org feed

[Aldebaran91]

Works really great but it doesn't update nugets if they are from another nuget-feed. Please add nuget.config support and don't forget to implement packageSourceMapping.

[OskarKlintrot]

Strange, I disabled my private feed in my global nuget.config and tried running the command on a project that uses a private feed and everything works. It works in our Azure Pipelines that doesn't have any global private sources setup but uses each solution nuget.config.

Package source mapping is something I want/need to implement when I manage to find time to implement support for CPM. I wonder if it's Package Source Mapping that breaks something in UpdatR and is the reason why it won't upgrade any packages in other feeds for you?

[Aldebaran91]

My nuget has a name which is also available in the nuget.org feed. It didn't update it. I just use this command

update TestSolution.sln

nuget.config file is in the same folder as the solution file.

[Aldebaran91]

Visual Studio uses fallback nuget.config files. Your app should use following nuget.config paths in this order

• nuget.config within *.sln or *.csproj folder path
• C:\Users\ { USER } \AppData\Roaming\NuGet\NuGet.Config
• C:Program Files (x86)\Nuget\Config\Microsoft.VisualStudio.FallbackLocation.config
• C:Program Files (x86)\Nuget\Config\Microsoft.VisualStudio.Offline.config

[OskarKlintrot]

That's not really how this tool works. I use NuGet's SDK and it's that SDK that will find all sources and then query them. I never read any configs at all iirc. With that said, something might be off with how I use the NuGet SDK. Would you mind provide a repo that replicates this bug? Something might also be wrong with how I try to stick to versions of packages that still support the TFM of the projects. Unfortunately, there's also the possibility that the bug you find is just NuGet/Home#13983 that is turning up in this tool as well.