aspire-orchestration

Manage Aspire AppHost lifecycle and recover from file locks and port conflicts.

46|6|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MarkItDotNet --skill aspire-orchestration-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-orchestration
Source: https://github.com/elbruno/ElBruno.MarkItDotNet/tree/main/.agents/skills/aspire-orchestration
Command: npx skills add https://github.com/elbruno/ElBruno.MarkItDotNet --skill aspire-orchestration-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manage Aspire AppHost lifecycle and recover from file locks, port conflicts, and orphaned processes that hinder development and CI workflows.

Core Features & Use Cases

  • Lifecycle management: start, stop, wait, ps, resource, integration, add, init, doctor, update, restore.
  • Safety guardrails and recovery: guidance for common error scenarios like MSB3491, CS2012, and port conflicts; provides disciplined workflows to cleanly stop and restart.
  • Handoff and discovery guidance: patterns for integrating with Aspireify and related skills; references for troubleshooting and best practices.

Quick Start

Start the Aspire AppHost with aspire start, then use aspire wait and resource commands to coordinate resources and recover from common issues.

Frequently Asked Questions about aspire-orchestration

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

FAQPage Schema
How do I recover from MSB3491 and CS2012 file lock errors during an Aspire AppHost build?

Recover from MSB3491 and CS2012 file lock errors by applying disciplined workflows to cleanly stop and restart the Aspire AppHost, terminating orphaned processes that hold locks before retrying your build.

How do I safely start and stop Aspire AppHost lifecycles in CI workflows?

Safely start and stop Aspire AppHost lifecycles in CI workflows by enforcing non-interactive agent usage patterns, utilizing aspire start to launch, aspire wait to coordinate resources, and specific stop commands to cleanly terminate.

What is the best way to resolve port conflicts and orphaned processes in Aspire?

Resolve port conflicts and orphaned processes in Aspire by leveraging built-in recovery workflows and lifecycle commands like aspire ps and aspire doctor to identify, troubleshoot, and safely terminate conflicting runtimes.

Does Aspire orchestration support non-interactive agent usage for automated pipelines?

Yes, Aspire orchestration supports non-interactive agent usage for automated pipelines by enforcing safe runtime patterns with aspire start and aspire wait, enabling reliable resource coordination and recovery without manual intervention.

Why does my Aspire AppHost hang or fail to stop cleanly during development?

Your Aspire AppHost may hang or fail to stop cleanly during development due to file locks, port conflicts, or orphaned processes, requiring structured recovery workflows to safely terminate resources and clean up before restarting.