dotnet-aspire

Orchestrate .NET Aspire AppHost topology with dependency wiring and startup ordering.

8|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-aspire-postpartum-genushyacinthus29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-aspire
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-aspire
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-aspire-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps software teams design and operate a .NET Aspire AppHost topology, enabling deterministic orchestration, testing, and deployment guidance across projects.

Core Features & Use Cases

  • Decide between project-based and file-based AppHost patterns and how to wire resources with WithReference and WaitFor.
  • Evaluate when to use first-party Aspire vs CommunityToolkit/Aspire for polyglot hosting, testing, and dashboard scenarios.
  • Guidance for local run, testing, and Azure deployment paths (ACA, App Service) while preserving a clean separation of concerns between orchestration and service logic.

Quick Start

Initialize Aspire support in your solution and run the AppHost locally to validate the topology.

Frequently Asked Questions about dotnet-aspire

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

FAQPage Schema
How do I orchestrate .NET Aspire AppHost topology for local development?

To orchestrate .NET Aspire AppHost topology, route between first-party Aspire integrations and CommunityToolkit/Aspire, applying proper ServiceDefaults scoping and explicit AppHost modeling to validate the topology locally.

Can I use WithReference and WaitFor for dependency wiring in .NET Aspire?

Yes, dependency wiring in .NET Aspire uses WithReference to connect resources and WaitFor to enforce startup ordering, supporting both project-based and file-based AppHost shapes for deterministic orchestration.

What's the best way to deploy .NET Aspire applications to Azure?

Deploying .NET Aspire applications to Azure requires clear deployment path selection between Azure Container Apps using azd or App Service, preserving clean separation of concerns between orchestration and service logic.

When should I use first-party Aspire integrations versus CommunityToolkit/Aspire?

First-party Aspire integrations cover standard hosting, testing, and dashboard scenarios, while CommunityToolkit/Aspire extends support for polyglot hosting and specialized community-driven integration requirements.

Does .NET Aspire support both project-based and file-based AppHost patterns?

Yes, .NET Aspire supports both project-based and file-based AppHost patterns, allowing teams to choose their preferred modeling approach while maintaining explicit AppHost topology and ServiceDefaults scoping.

How do I test .NET Aspire AppHost configurations and dashboard usage?

Testing .NET Aspire AppHost configurations involves evaluating integration choices, validating topology through local runs, and leveraging dashboard usage guidance to ensure deterministic orchestration across resources.