部署与云服务
aspire
Build, upgrade, and operate Aspire 13.5.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, apphost.mts, createBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
managedcode · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add managedcode/dotnet-skills --skill aspire技能说明
name: aspire description: "Build, upgrade, and operate Aspire 13.5.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, apphost.mts, createBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."
Aspire
Trigger On
Aspire.AppHost.Sdk,Aspire.Hosting.*,DistributedApplication.CreateBuilder,apphost.mts,createBuilder,WithReference,WaitFor,AddProject,addNodeApp,addViteApp,AddRedis,AddPostgres,aspire run,aspire init,aspire add, oraspire updateAspire.Hosting.Testing,DistributedApplicationTestingBuilder, or a test harness that mixes an Aspire AppHost withWebApplicationFactory- orchestrating multiple services and resources with an AppHost for local development or cloud deployment
- setting up
ServiceDefaults, service discovery, OpenTelemetry, health checks, or the Aspire Dashboard - choosing between official first-party Aspire integrations and
CommunityToolkit/Aspire - upgrading older 8.x or 9.x Aspire solutions to the current CLI and AppHost SDK model
- wiring polyglot services into an Aspire topology, especially when Go, Bun, Java, Python, or extra dev-time tools enter the picture
Workflow
- Classify the task first: new AppHost creation, existing-solution enlistment, integration wiring, testing and observability, deployment, or version upgrade.
- Prefer the current Aspire toolchain. Choose a C# AppHost for .NET-first repositories or a TypeScript
apphost.mtsfor JavaScript/TypeScript-first repositories; both are first-class in 13.5. Use the Aspire CLI and current SDK-generated app model instead of writing new guidance around the deprecated legacy workload. - Treat 13.5.x releases as the current CLI-first app model. Keep the Aspire CLI,
Aspire.AppHost.Sdk, and closely coupled hosting or testing packages on the same line, then rerun the AppHost and deployment checks afteraspire update. - Keep the AppHost code-first and topology-focused. Model services, resources, dependencies, endpoints, lifetimes, and parameters there; keep business logic out.
- Keep
ServiceDefaultsnarrow. It exists for telemetry, health checks, resilience, and service discovery, not shared domain models or general utility code. - Prefer official first-party Aspire integrations when they cover the requirement. Use
CommunityToolkit/Aspireonly when the capability gap is real: unsupported language hosts, extra dev infrastructure, or extension packages the official project does not provide. - Validate the whole distributed system, not one project in isolation. Local success means the AppHost starts cleanly, dependencies resolve through
WithReference, the dashboard shows the expected resource graph, and end-to-end tests can exercise the topology. - For integration tests, keep one shared AppHost fixture per test session. Use
Aspire.Hosting.Testingto boot the distributed app, createHttpClientor SignalR clients from the AppHost, and layerWebApplicationFactoryon top only when tests need direct Host DI, grains, or runtime services. Fixture sharing amortizes startup and must not serialize tests; keep consumers parallel and isolate their mutable state. - When publishing, switch from local containers or emulators to managed resources deliberately and verify which services truly need external endpoints.
Architecture
flowchart LR
A["Distributed-app task"] --> B{"Need code-first orchestration?"}
B -->|No| C["Stay in service-level skills such as ASP.NET Core, Worker, or Orleans"]
B -->|Yes| D["Create or update the AppHost"]
D --> E["Model resources and services with `WithReference` and `WaitFor`"]
E --> F{"Official Aspire integration exists?"}
F -->|Yes| G["Use first-party Aspire integration"]
F -->|No or gap remains| H["Evaluate `CommunityToolkit/Aspire`"]
G --> I["Apply `ServiceDefaults`, dashboard, and tests"]
H --> I
I --> J{"Publishing now?"}
J -->|No| K["Run locally with `aspire run` or the AppHost project"]
J -->|Yes| L["Choose `azd`, App Service, or the CLI deploy/publish pipeline"]
Current Guidance
- AppHost shape: recognize three current first-class forms: an SDK-style C# AppHost project using
Aspire.AppHost.Sdk/<version>, a file-based C#apphost.cs, or a TypeScriptapphost.mts. For TypeScript,aspire init --language typescriptwritesaspire.config.jsonand the generated.aspire/modules/SDK; do not hand-edit generated modules, and runaspire restoreafter package/integration changes. - TypeScript AppHosts: use the async lower-camel-case app model (
createBuilder,addNodeApp,addViteApp,withReference,waitFor,build().run()). In an existing repository with a rootpackage.json, expect the CLI to create a nestedaspire-apphost/package so the application and orchestration toolchains stay separate. - Polyglot hosting: Aspire 13.4 adds first-party Go and Bun support, and 13.5 makes TypeScript AppHosts generally available. Prefer the official hosting surface for new Go, Bun, or TypeScript resources before considering older toolkit integrations; keep community integrations for languages and capabilities that still have a real first-party gap.
- CLI entry points: use
aspire newfor starter projects,aspire initto add Aspire support to an existing solution or create a single-file AppHost,aspire addto add integrations or starter pieces,aspire runfor local orchestration,aspire start/aspire stop/aspire psfor detached lifecycle management,aspire describefor l