Problem
Several pages and sidebar labels use .NET-specific terminology in contexts that should be language-neutral. A TypeScript/JavaScript developer navigating the docs encounters NuGet packages, .csproj files, dotnet CLI commands, and C#-only concepts like "service defaults" presented as universal Aspire features.
Sidebar labels that are misleadingly generic
| Current label |
Problem |
Suggestion |
| Aspire SDK |
Page is 100% about Aspire.AppHost.Sdk NuGet + .csproj |
Rename to "Aspire SDK (C#)" or scope under C# AppHost |
| Aspire templates |
Page is about .NET dotnet new templates |
Rename to "Aspire templates (C#)" or scope similarly |
| Service defaults |
.csproj project with AddServiceDefaults() — C#-only |
Clarify as C#-specific in label or page intro |
Content issues
NuGet references in multi-language AppHost page
get-started/app-host.mdx — The Python, JavaScript, Go, and Java pivots mention "NuGet package" which is confusing for non-.NET developers. These are packages for the AppHost, not the target language.
Service defaults in Fundamentals
fundamentals/service-defaults.mdx, fundamentals/health-checks.mdx — Presented as universal concepts but documented entirely with C# code (AddServiceDefaults(), MapDefaultEndpoints(), .csproj projects).
.csproj in getting started
get-started/add-aspire-existing-app.mdx — Assumes all projects are .NET with .csproj file trees.
dotnet run in pipelines
get-started/pipelines.mdx — Generic deployment pipeline page uses dotnet run --project examples.
Glossary defines "Projects" as .NET only
get-started/glossary.mdx — "Projects" defined as ".NET applications, services, APIs" — excludes Python/JS/Go/Java.
C# DevKit in VS Code extension page
get-started/aspire-vscode-extension.mdx — C# DevKit mentioned generically, not scoped to C# AppHost context.
What is NOT a problem (already fixed)
- Prerequisites page — has C#/TypeScript pivots ✅
- First-app page — has C#/Python/JavaScript pivots ✅
- Install CLI page — no .NET dependency mentioned ✅
- Landing page — language-neutral ✅
Problem
Several pages and sidebar labels use .NET-specific terminology in contexts that should be language-neutral. A TypeScript/JavaScript developer navigating the docs encounters NuGet packages,
.csprojfiles,dotnetCLI commands, and C#-only concepts like "service defaults" presented as universal Aspire features.Sidebar labels that are misleadingly generic
Aspire.AppHost.SdkNuGet +.csprojdotnet newtemplates.csprojproject withAddServiceDefaults()— C#-onlyContent issues
NuGet references in multi-language AppHost page
get-started/app-host.mdx— The Python, JavaScript, Go, and Java pivots mention "NuGet package" which is confusing for non-.NET developers. These are packages for the AppHost, not the target language.Service defaults in Fundamentals
fundamentals/service-defaults.mdx,fundamentals/health-checks.mdx— Presented as universal concepts but documented entirely with C# code (AddServiceDefaults(),MapDefaultEndpoints(),.csprojprojects)..csprojin getting startedget-started/add-aspire-existing-app.mdx— Assumes all projects are .NET with.csprojfile trees.dotnet runin pipelinesget-started/pipelines.mdx— Generic deployment pipeline page usesdotnet run --projectexamples.Glossary defines "Projects" as .NET only
get-started/glossary.mdx— "Projects" defined as ".NET applications, services, APIs" — excludes Python/JS/Go/Java.C# DevKit in VS Code extension page
get-started/aspire-vscode-extension.mdx— C# DevKit mentioned generically, not scoped to C# AppHost context.What is NOT a problem (already fixed)