Skip to content

Fix TFM/Aspire version selection in templates #10009

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 23, 2025

Conversation

DamianEdwards
Copy link
Member

Description

Corrects a bunch of scenarios regarding selecting TFM and Aspire version combinations. If net10.0 is selected as TFM then Aspire 9.4 should be the only valid choice. Manually tested all combinations in VS via NPD and "Add .NET Aspire orchestration" scenarios.

Fixes #9950

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • No
  • Did you add public API?
    • No
  • Does the change make any security assumptions or guarantees?
    • No
  • Does the change require an update in our Aspire docs?
    • No

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR enforces that when net10.0 is selected, only the .NET Aspire 9.4 option is available by removing all references and configuration entries for Aspire 9.3 where it no longer applies. Key changes include:

  • Removal of the Aspire 9.3 choice and its related condition blocks from template.json files in multiple templates.
  • Updates to localization files across various languages to reflect the removal of the 9.3 option.
  • A change in the package reference version in the 9.4 xUnit test project CSProj file.

Reviewed Changes

Copilot reviewed 109 out of 109 changed files in this pull request and generated 1 comment.

File Description
src/Aspire.ProjectTemplates/templates/aspire-xunit/9.4/Aspire.Tests.1.csproj Updated the package reference for Aspire.Hosting.Testing to use a placeholder version.
*.template.config/template.json (across aspire-xunit, aspire‑starter, aspire‑servicedefaults, aspire‑nunit, aspire‑mstest) Removed the choice for Aspire 9.3 and its corresponding condition entries.
.template.config/localize/templatestrings..json (all languages) Updated localization entries to maintain consistency with the removal of the 9.3 option.

Copy link
Contributor

@phenning phenning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@DamianEdwards DamianEdwards merged commit a7b3a3d into main Jun 23, 2025
252 checks passed
@DamianEdwards DamianEdwards deleted the damianedwards/empty-template-fix branch June 23, 2025 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[AspireE2E] When creating a web project with Aspire orchestration, Aspire version 9.3 creates an Apphost project with version 9.4 by default.
2 participants