aspire-orchestration

To resolve MSB3491 and CS2012 file lock errors during Aspire AppHost startup, apply guided recovery sequences and resource-safe cleanup. The orchestration detects these build failures automatically and executes non-interactive recovery patterns to clear locked files.

The best way to manage Aspire AppHost lifecycle safely is using orchestrated start, stop, and wait commands with built-in guardrails. This enforces wait conditions and resource-safe cleanup, preventing orphaned processes during standard operations and across git worktrees.

To fix port conflicts when running Aspire AppHost in git worktrees, apply isolated operation and resource-safe cleanup. The orchestration detects port conflicts during startup and executes recovery patterns to ensure safe, non-interactive process isolation across worktrees.

Yes, you can run Aspire orchestration non-interactively with JSON formatting. The lifecycle management supports non-interactive operation and JSON output, enabling automated describe, wait, and recovery workflows for AppHost resources without manual intervention.

Aspire AppHost fails to start with orphaned processes due to incomplete shutdowns leaving active resource locks. The orchestration cleans them up by applying resource-safe cleanup patterns and aspire wait conditions to safely terminate orphaned processes before restarting.