[release/13.1] Fix template version parsing for .NET 10.0 SDK separator change

[JamesNK]

Customer Impact

aspire init fails with .NET 10.0.200 (currently preview, releasing in early March) because the SDK changed the output text, and Aspire fails to parse the new output text.

Fix is to support both formats.

Testing

• Automated testing
• Manual testing aspire init (TODO - waiting on CI to build PR CLI to test end-to-end)

Risk

Low

Regression?

Yes, aspire init use to always work. Now it will fail with new .NET SDK versions.

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 14698

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 14698"

[Copilot]

Pull request overview

This PR updates Aspire CLI’s template-install stdout parsing to handle the .NET 10 SDK change from :: to @ as the package/version separator, preventing aspire init failures on newer SDKs.

Changes:

• Update DotNetCliRunner parsing logic to accept @ separator (with :: fallback).
• Expose the parsing helper as internal to enable direct unit testing.
• Add new unit tests covering both separators and invalid/missing formats.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/Aspire.Cli/DotNet/DotNetCliRunner.cs	Accept @ as the primary template version separator, fallback to ::, and make parser callable from tests.
tests/Aspire.Cli.Tests/DotNet/DotNetCliRunnerTests.cs	Add theory-based coverage for parsing both new and old SDK output formats.

[JamesNK]

Build failure:

Downloading 'https://builds.dotnet.microsoft.com/dotnet/scripts/v1/dotnet-install.sh'
Attempting to install 'sdk v10.0.101' from public_location.
dotnet-install: Attempting to download using primary link https://builds.dotnet.microsoft.com/dotnet/Sdk/10.0.101/dotnet-sdk-10.0.101-linux-x64.tar.gz
dotnet-install: Remote file https://builds.dotnet.microsoft.com/dotnet/Sdk/10.0.101/dotnet-sdk-10.0.101-linux-x64.tar.gz size is 239025495 bytes.
dotnet-install: Extracting archive from https://builds.dotnet.microsoft.com/dotnet/Sdk/10.0.101/dotnet-sdk-10.0.101-linux-x64.tar.gz
dotnet-install: Downloaded file size is 239025495 bytes.
dotnet-install: The remote and local file sizes are equal.
dotnet-install: Installed version is 10.0.101
dotnet-install: Adding to current process PATH: /home/runner/work/aspire/aspire/.dotnet. Note: This change will be visible only when sourcing script.
dotnet-install: Note that the script does not resolve dependencies during installation.
dotnet-install: To check the list of dependencies, go to https://learn.microsoft.com/dotnet/core/install, select your operating system and check the "Dependencies" section.
dotnet-install: Installation finished successfully.
[0] ERROR: Exception in Command Processing for EventSource Dotnet-dev-certs: Event WslWindowsTrustSucceeded was assigned event ID 115 but 113 was passed to WriteEvent.
Trusting the HTTPS development certificate was requested. Trust is per-user and may require additional configuration. See https://aka.ms/dev-certs-trust for more information.
There was an error trusting the HTTPS developer certificate. It will be trusted by some clients but not by others.
Error: Process completed with exit code 4.

I think this is a bug in the .NET SDK. Does it need to be updated in 13.1 branch?

[JamesNK]

PR also updates .NET SDK and has workaround for this issue: dotnet/aspnetcore#65391