"Install the Aspire Templates" section should be clear it's referring specifically to dotnet #1059

Activity

1. Alex Crome (afscrome)

   changed the title [-]"Install the Aspire Templates" should be clear it's refering specifically to[/-] [+]"Install the Aspire Templates" section should be clear it's referring specifically to `dotnet`[/+] on May 25, 2026
2. IEvangelist commented on Jun 2, 2026

   

   David Pine (IEvangelist)

   on Jun 2, 2026

   Member

   More actions

   Triage → @Copilot

   Page: https://aspire.dev/get-started/aspire-sdk-templates/ → src/frontend/src/content/docs/get-started/aspire-sdk-templates.mdx

   Scope

   1. Make the "Install the Aspire Templates" section explicit that it covers the .NET templates installed via dotnet new install Aspire.ProjectTemplates. The current copy reads like it applies to all language SDKs.
   2. Remove the phrase "Aspire workload" — workloads are no longer used; templates ship as a NuGet package.
   3. Prefer/lead with the aspire new flow where the CLI handles template installation transparently; keep the dotnet new install path as a secondary/.NET-specific section.

   Acceptance

   • Section header clarifies .NET scope (e.g. "Install the .NET project templates").
   • No remaining references to "Aspire workload" in this page.
   • aspire new is the primary path; dotnet new install is documented as the .NET fallback.
   • No unrelated content changes.
3. David Pine (IEvangelist)

   assigned

   Copilot

   and

   David Pine (IEvangelist)

   on Jun 2, 2026
4. Copilot

   linked a pull request that will close this issueClarify template installation guidance: CLI-first flow with .NET fallback #1156on Jun 2, 2026