WorkerExtensions.csproj trying to restore from private nuget feed, unsuccessfully

[1kevgriff]

I hope this is the right place for this question.

I have this recurring problem with our local Functions app trying to build. We recently moved to .NET 6 Isolated to support some future product features.

On build, I get this error:

1>C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\CommonExtensions\Microsoft\NuGet\NuGet.targets(132,5): warning : No Authorization header detected
1>Retrying 'FindPackagesByIdAsync' for source 'https://nuget.pkg.github.com/{{ ourorg }}/download/microsoft.azure.webjobs.extensions.durabletask/index.json'.
1>Response status code does not indicate success: 401 (Unauthorized).
1>C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\CommonExtensions\Microsoft\NuGet\NuGet.targets(132,5): warning : No Authorization header detected
1>C:\Users\kevin\AppData\Local\Temp\l20wov0k.lk5\WorkerExtensions.csproj : error NU1301: Failed to retrieve information about 'Microsoft.Azure.WebJobs.Extensions.DurableTask' from remote source 'https://nuget.pkg.github.com{{ ourorg }}/download/microsoft.azure.webjobs.extensions.durabletask/index.json'.
1>Failed to restore C:\Users\kevin\AppData\Local\Temp\l20wov0k.lk5\WorkerExtensions.csproj (in 5.86 sec).

I'm not sure why WorkerExtensions.csproj is trying to look at our private Nuget feed for that package.

Functions.csproj

<Project Sdk="Microsoft.NET.Sdk">
	<PropertyGroup>
		<TargetFramework>net6.0</TargetFramework>
		<AzureFunctionsVersion>v4</AzureFunctionsVersion>
		<OutputType>Exe</OutputType>
	</PropertyGroup>
	<ItemGroup>
		<PackageReference Include="Microsoft.Azure.Functions.Extensions" Version="1.1.0" />
		<PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.10.0" />
		<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.DurableTask" Version="1.0.0-rc.1" />
		<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.0.13" />
		<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Storage" Version="5.0.1" />
		<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Timer" Version="4.1.0" />
		<PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.7.0" OutputItemType="Analyzer" />
		<PackageReference Include="Microsoft.DurableTask.Generators" Version="1.0.0-preview.1" OutputItemType="Analyzer" />
	</ItemGroup>

    <!-- other stuff removed for brevity -->

</Project>

[kshyju]

Are you having trouble when trying to build/restore packages using Visual studio? Do you have the nuget.org package source (https://api.nuget.org/v3/index.json) enabled?

If you are trying to restore using "Manage Nuget packages" tab of the project, do you have "nuget.org" package source selected?

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[1kevgriff]

@kshyju Regular restore works fine. This is only trying to build our project if our private repo is enabled:

In the above, I usually have to disable our package source for it to work. nuget.org is typically the default (or all if I'm in the nuget explorer)

[jviau]

@1kevgriff I believe the issue is that part of the build process will create a temporary project and invoke dotnet restore on that. This target is not inheriting Visual Studio auth for the restore operation. Can you try installing Nuget Credential Provider and trying again? You probably need to include the -netfx switch).

[madhavireddythirumuru]

Hi @1kevgriff, I could resolve similar issue by following the below work around steps.

1. Update package source to use only the public nuget source "https://api.nuget.org/v3/index.json" and not any of the private feeds.
2. Restore nuget packages and Rebuild the solution/project.
3. When build is successful, change the package source back to your private feed.
4. Now build the solution once again.
   This should solve the problem

One more alternative is :

1. Create a similar project with same dependencies in a separate solution with package source as public nuget feed.
2. Build the solution.
3. Change the package source to private nuget feed and rebuild the solution
4. Now go the previous solution where this issue happened first and rebuild the solution (with out changing the feed)
   Build will be successful this time.

I hope these steps would help you resolve the issue.