Unable to find package `Microsoft.Extensions.ServiceDiscovery` with version (>= 10.6.0-preview.1.26210.2) after creating blazor-wasm-servicedefaults project

[jinzhao1127]

REGRESSION INFO: New feature on 11.0 P4, not repro in previous build

INSTALL STEPS:

1. Clean Win 11 25h2 x64
2. Install Latest 11.0 P4 build from https://release.dot.net/
3. Apply Feed

Platform

• Windows
• macOS
• Linux

Repro Steps

1. Open up a normal Command Prompt (Terminal)
2. Create a blazor-wasm-servicedefaults app and run it.

   dotnet new blazor-wasm-servicedefaults  -o servicedefaults
   

Actual Result

error NU1102 Unable to find package Microsoft.Extensions.ServiceDiscovery with version (>= 10.6.0-preview.1.26210.2)

Error Log

 C:\Users\v-zhajin\servicedefaults1\servicedefaults1.csproj : error NU1102:
      Unable to find package Microsoft.Extensions.ServiceDiscovery with version (>= 10.6.0-preview.1.26210.2)
        - Found 36 version(s) in nuget.org [ Nearest version: 10.5.0 ]
        - Found 0 version(s) in Microsoft Visual Studio Offline Packages
        - Found 0 version(s) in C:\Program Files\dotnet\library-packs
        - Found 0 version(s) in net11
Restore failed.
Post action failed.
Manual instructions: Run 'dotnet restore'.

Expected Result
There is not any error.

Note:

1. After change the packages version to 10.5.0, it will work.
   https://www.nuget.org/packages/Microsoft.Extensions.ServiceDiscovery

[jinzhao1127]

@Youssef1313, could you look at this issue?
cc: @balachir

[github-actions]

Triage Summary

Area: area-commandlinetools — The issue is with the blazor-wasm-servicedefaults project template generating a .csproj that references a version of Microsoft.Extensions.ServiceDiscovery (10.6.0-preview.1.26210.2) that hasn't been published to NuGet.org yet, causing a restore failure.

Type: bug — A newly created project from a template immediately fails to restore because the referenced package version does not exist publicly.

Regression Info

• Previously working version: .NET 11.0 (prior build, pre-P4)
• Broken since: .NET 11.0 Preview 4
• The blazor-wasm-servicedefaults template generates a reference to Microsoft.Extensions.ServiceDiscovery >= 10.6.0-preview.1.26210.2, but only versions up to 10.5.0 are available on NuGet.org. Downgrading to 10.5.0 works as a workaround.

Potential Duplicates

• None found

Notes

• The Microsoft.Extensions.ServiceDiscovery package is part of the .NET Aspire stack (owned by dotnet/aspire), but the template itself lives in aspnetcore. The fix likely requires either updating the template to reference the correct/available version, or ensuring the package is published before the SDK preview ships.
• The issue may also affect other servicedefaults-based templates.

Generated by Issue Triage Agent for dotnet/aspnetcore for issue #66594 · ● 143.7K · ◷

[Youssef1313]

I feel like the right way to fix this is adjusting our insertions. I would expect insertions from extensions repo to release branch of aspnetcore repo to go through the corresponding .NET version channel, and insertions to main branch of aspnetcore to go through .NET Core Tooling Dev channel. In addition, the default channels of extensions repo don't appear to be setup correctly. I'll start an internal discussion.