aspire

Orchestrates Aspire distributed applications using the Aspire CLI for starting, debugging, and managing resources.

28|8|Updated Feb 21, 2022
One-click install
npx skills add https://github.com/Avanade/CoreEx --skill aspire-avanade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/Avanade/CoreEx/tree/main/.github/skills/aspire
Command: npx skills add https://github.com/Avanade/CoreEx --skill aspire-avanade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running and debugging Aspire distributed applications requires remembering many CLI commands and workflows, and mistakes like restarting the entire AppHost for a single resource change waste time. This Skill provides the full Aspire CLI command reference, key workflows, and environment guidance so agents and developers operate the AppHost correctly. ## Core Features & Use Cases - App Lifecycle Management: Start, stop, restart, and isolate AppHost instances, including worktree-safe isolated runs with aspire start --isolated. - Resource Operations: List resources, wait for health, rebuild individual .NET project resources, and run resource-specific commands without full restarts. - Debugging & Observability: Inspect console logs, structured OpenTelemetry logs, and distributed traces to diagnose failures before changing code. - Use Case: After modifying a .NET API project in an Aspire app, run aspire resource products-api rebuild to rebuild and restart only that resource, then use aspire otel logs products-api to verify it is healthy. ## Quick Start Ask the agent to start the Aspire app in isolated mode and wait until the API resource is healthy before running tests.

Frequently Asked Questions about aspire

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start an Aspire distributed application from the CLI?▼

Run `aspire start` to launch the AppHost in the background. When working in a git worktree, use `aspire start --isolated` to avoid port conflicts and sharing state with other running instances.

How do I restart a single .NET project in Aspire without restarting the AppHost?▼

Use `aspire resource <name> rebuild` to rebuild and restart only that .NET project resource. Restarting the entire AppHost is only needed when the AppHost project itself changes.

How do I view logs and traces for an Aspire resource?▼

Use `aspire logs <resource>` for console output, `aspire otel logs <resource>` for structured logs, and `aspire otel traces <resource>` for distributed traces. You can also filter logs by trace ID with `aspire otel logs --trace-id <id>`.

When should I use the Aspire CLI versus the dotnet CLI?▼

Use the Aspire CLI for Aspire-specific operations like starting the orchestrated app, waiting for resource health, and viewing telemetry. Use the dotnet CLI directly for non-Aspire tasks such as building, testing, or running a single project.

Why should I avoid restarting the whole Aspire AppHost after a code change?▼

A full restart is only required when the AppHost project changes, since the resource graph is redefined. For compiled .NET resources, `aspire resource <name> rebuild` coordinates stop, build, and restart for just that resource, which is faster.

Can I add new integrations to an Aspire AppHost from the CLI?▼

Yes. Use `aspire docs search` to find integration guidance, then `aspire add` to add the integration package to the AppHost. Restart the app with `aspire start` afterward for the new resource to take effect.