Description

Aspire dropped the ".NET" moniker some time ago. This PR updates the templates and docs accordingly. In some cases, this may improve discoverability, such as when filtering by template "tag" in the CLI 👇 or Project Type in Visual Studio.

dotnet new list --tag aspire

Current behavior:

No templates found matching: --tag='aspire'.

Desired behavior:

Template Name                 Short Name            Language  Tags
----------------------------  --------------------  --------  ----------------------------------------------------------
TUnit Aspire Starter Project  TUnit.Aspire.Starter  [C#]      Test/TUnit/Asp/ASP.NET/Blazor/Aspire/Cloud/Playwright
TUnit Aspire Test Project     TUnit.Aspire.Test     [C#]      Common/Test/TUnit/Aspire/Cloud

Related Issue

I didn't create an issue for this.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Performance improvement
• Refactoring (no functional changes)

Checklist

Required

• I have read the Contributing Guidelines
• If this is a new feature, I started a discussion first and received agreement
• My code follows the project's code style (modern C# syntax, proper naming conventions)
• I have written tests that prove my fix is effective or my feature works

TUnit-Specific Requirements

• Dual-Mode Implementation: If this change affects test discovery/execution, I have implemented it in BOTH:
  • Source Generator path (TUnit.Core.SourceGenerator)
  • Reflection path (TUnit.Engine)
• Snapshot Tests: If I changed source generator output or public APIs:
  • I ran TUnit.Core.SourceGenerator.Tests and/or TUnit.PublicAPI tests
  • I reviewed the .received.txt files and accepted them as .verified.txt
  • I committed the updated .verified.txt files
• Performance: If this change affects hot paths (test discovery, execution, assertions):
  • I minimized allocations and avoided LINQ in hot paths
  • I cached reflection results where appropriate
• AOT Compatibility: If this change uses reflection:
  • I added appropriate [DynamicallyAccessedMembers] annotations
  • I verified the change works with dotnet publish -p:PublishAot=true

Testing

• All existing tests pass (dotnet test)
• I have added tests that cover my changes
• I have tested both source-generated and reflection modes (if applicable)

Additional Notes