Open costin-zaharia-sonarsource opened 7 months ago
Thanks for reporting will check and update.
@fabiocav pls comment and validate.
Come on this has been almost 7 mos we need a solution to this. This breaks it so upgrading this on the CI is difficult -- please prioritize a fix for this issue.
We have also encountered this issue. Azure Functions generates a project called WorkerExtensions.csproj in a temp folder. When WorkerExtensions.csproj is built, packages are restored using global NuGet settings instead of project NuGet settings. WorkerExtensions.csproj should be built using the same NuGet settings as the Azure Functions project.
Azure Functions project cannot be properly restored if there is no machine-level package source defined.
Steps to reproduce:
%appdata%\NuGet\NuGet.Config
and remove all package sourcesdotnet restore
(it has to bedotnet restore
sincenuget restore
works)Actual behavior
The following errors are returned:
Expected behavior
dotnet restore
should consider the local nuget configuration file and use it.Additional notes
As far as I can tell, the problem only appears when referencing:
Workaround
Ensure that
%appdata%\NuGet\NuGet.Config
has a valid package source defined.