Clarify that --isolated supports parallel copies of an AppHost in different directories
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp
- Domain
- cli, documentation
Research direction
Start by locating the help text for aspire run, aspire start, and run --detach, then check how each command handles repeated invocations from the same AppHost path. Update the help consistently to explain the supported separate-directory workflow and same-path behavior, with a short two-worktree example. Done when all three help outputs clearly describe these cases.
Written by the indexing model from the issue text.
Description
Clarify that --isolated supports parallel copies of an AppHost in different directories
Target: microsoft/aspire
Both aspire run --help and aspire start --help describe --isolated as:
Run in isolated mode with randomized ports and isolated user secrets, allowing multiple instances to run simultaneously
This sounds like I can start two instances from the same checkout. In a local test, running:
aspire start --apphost apphost.cs --isolated --no-build --non-interactive --format Json
while that AppHost was already running under the VS Code debugger printed:
Stopping previous instance (AppHost PID: ..., CLI PID: ...)
The previous instance stopped and the new instance started instead. This was on macOS with Aspire SDK 17.0.0. We haven't separately reproduced two concurrent foreground aspire run --isolated commands.
The intended contract has been confirmed: parallel isolated runs use copies of the same AppHost in different directories, such as separate Git worktrees. Isolation doesn't enable multiple concurrent instances from the same AppHost path.
Can the help say that explicitly? 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.
Please clarify this consistently for run, start, and run --detach, including whether repeating a command from the same path replaces the existing instance. A short two-worktree example would make the supported workflow clear.
Related docs follow-up: microsoft/aspire.dev#2184 covers the separately maintained aspire run and aspire start reference pages.
- Dominant language
- C#
- Stars
- 6.4k
- Forks
- 1k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 466
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/aspire
-
area-templates triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/aspire#22356 · 1 comment ·
Maintainers usually reply within 1 day
-
area-meta
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
microsoft/aspire#22336 · 1 comment ·
Maintainers usually reply within 1 day
-
Copilot telemetry hook write replaces all of ~/.copilot/hooks/aspire-telemetry.jsonPossibly taken @anandt1201 claimed this today. Openneeds-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
microsoft/aspire#22144 · 1 comment ·
Maintainers usually reply within 1 day
-
Aspire.Hosting.Yarp flattens TimeSpan cluster settings (ActivityTimeout, health-check intervals) into per-property env vars the YARP container ignoresPossibly taken @itsrayeedscodespace claimed this 8 days ago. Openarea-integrations
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in microsoft/aspire
Similar issues
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PowerShell/PowerShell#28432 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/aspire.dev#2184 ·
Maintainers usually reply within 2 days
-
area-controls-refreshview platform/ios s/triaged
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dotnet/maui#40314 · 1 reaction ·
Maintainers usually reply within 1 day
-
Needs: Triage (Functions) v5 v5-preview5
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Azure/azure-functions-core-tools#5918 ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elsa-workflows/elsa-foundation#4712 · 1 comment ·
Maintainers usually reply within 1 day