NuGet error when restoring locally

[smirkingsquiggly]

I'm trying to restore and build Aspire locally, but I get this error:

Version 17.13.1 of package dotnet-coverage is not found in NuGet feeds https://dnceng.pkgs.visualstudio.com/public/_packaging/dotnet9-transport/nuget/v3/index.json.

This happens when I run restore.cmd or build.cmd.
I've cleared out my local NuGet cache but this didn't solve it.
Is there an issue with the dotnet9-transport package source?

[davidfowl]

cc @joperezr

[joperezr]

Interesting, @RussKie could you take a look? I can't repro this but more importantly why do we still have dotnet-coverage tool being restored to begin with? I thought that was removed.

@smirkingsquiggly can you share the exact build.cmd command you are running?

[RussKie]

@joperezr: no, we still have it declared:

aspire/.config/dotnet-tools.json

Line 5 in 7cec38b

"dotnet-coverage": {

...and used:

aspire/eng/pipelines/templates/BuildAndTest.yml

Lines 80 to 82 in 7cec38b

	- script: ${{ parameters.dotnetScript }} dotnet-coverage collect
	--output ${{ parameters.repoTestResultsPath }}/NonHelix.cobertura.xml
	"${{ parameters.buildScript }} -testnobuild -test -configuration ${{ parameters.buildConfig }} /bl:${{ parameters.repoLogPath }}/tests.binlog /maxcpucount:1 /p:BuildInParallel=false $(_OfficialBuildIdArgs)"

@smirkingsquiggly: the tool is located in https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet-public/NuGet/dotnet-coverage/overview/17.13.1.
The error suggests you may be having some local setup issues (e.g., blocked off dotnet-public feed).

[joperezr]

@RussKie are there any other logs that @smirkingsquiggly can provide for us to understand if there are indeed some local setup issues?

[smirkingsquiggly]

Last week I added package source mappings to get around restore errors after running restore.cmd from the repo root.
These are now stored in my local NuGet.config in the Aspire folder.
I took dotnet-public as the leading package source, not sure if that's correct.
To get around the dotnet-coverage error, I had to add the following package source mappings:

<packageSourceMapping>    
  <packageSource key="dotnet-public">
    <!-- FluentUI is present on both public an internal dotnet feeds. Prefer public feed -->
    <package pattern="dotnet-coverage" />
    <package pattern="powershell" />
    <package pattern="sn" />
    ...
  </packageSource>
</packageSourceMapping>

Now I'm stuck with version errors like the one below:

\aspire\tests\Aspire.Azure.Messaging.WebPubSub.Tests\Aspire.Azure.Messaging.WebPubSub.Tests.csproj : error NU1603: Warning As Error: Aspire.Azure.Messaging.WebPubSub.Tests depends on OpenTelemetry.Extensions.Hosting (>= 1.9.0) but OpenTelemetry.Extensions.Hosting 1.9.0 was not found. OpenTelemetry.Extensions.Hosting 1.11.2 was resolved instead.

I also added the package source mapping for the OpenTelemetry packages to NuGet.config.
Are those packages not available in the dotnet-public package source?

Here's the output of restore.cmd:
restore.txt

Here's my current NuGet.config:
NuGet.config.txt

[joperezr]

I would suggest not changing the aspire root's NuGet.config and it's configured mappings. As part of our CI builds, we run on machines that are clean and don't have a package cache, so if there is a miss-configuration with NuGet.config or package mappings it should be caught there, so by making sure you don't make edits to it locally, restore should work. Can you please revert (or stash) the changes you have on that file and try to restore again to see if the failures disappear?

[RussKie]

I've looked at the attached nuget.config, and the issue is in it. Packages are only restored from "dotnet-public" feed, no other feed is used to restore packages from.
Please refer to https://learn.microsoft.com/nuget/consume-packages/package-source-mapping.

[smirkingsquiggly]

@joperezr , @RussKie :
I just reviewed this problem once more and cloned the repo anew on my system.
It turned out that the NuGet.config in my \AppData\Roaming\NuGet folder was conflicting with the Aspire one.
The same dotnet-public package source was configured in there, I removed it.
But I think the bigger problem was that some packages that Aspire needs were also mapped to the nuget.org package source.
I've cleaned up my general NuGet.config as much as possible.

After that, I could successfully run restore.cmd and also build the solution in Visual Studio.
Thanks for helping out!