You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Clarify worktree and same-path behavior for --isolated in the CLI reference #2184
Neither explains that those instances must come from different directories, such as separate worktrees/checkouts. That intended contract has now been confirmed.
In a local test, aspire start --apphost apphost.cs --isolated --no-build --non-interactive --format Json stopped the existing VS Code-debugged instance at that path before starting its replacement. This was on macOS with Aspire SDK 17.0.0. We haven't separately reproduced two concurrent foreground aspire run --isolated commands.
Update both reference pages:
Say that parallel isolated runs require copies of the same AppHost in different directories, typically separate worktrees/checkouts.
Explain what happens when the same command is repeated from the same path.
Distinguish run, start, and run --detach if their behavior differs.
Include a concrete supported side-by-side example.
Suggested wording:
Run with randomized ports and isolated user secrets, allowing copies of the same AppHost in different directories, such as separate Git worktrees, to run simultaneously. This does not enable multiple concurrent instances from the same AppHost path.
These pages contain their own checked-in descriptions in:
Activity