`dotnet run --operation publish` should exit on failure
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Describe the bug
If you `dotnet run` an apphost with `--operation publish` in main, it seems to get stuck.
> dotnet run --project .\playground\Redis\Redis.AppHost\ --operation publish
```
Using launch settings from .\playground\Redis\Redis.AppHost\Properties\launchSettings.json...
Building...
⠋ Starting dashboard...
```
In publish mode, why is aspire even trying to start the dashboard?
### Expected Behavior
_No response_
### Steps To Reproduce
In main
1. `dotnet run --project .\playground\Redis\Redis.AppHost\ --operation publish`
### Exceptions (if any)
```
Using launch settings from .\playground\Redis\Redis.AppHost\Properties\launchSettings.json...
Building...
⠋ Starting dashboard...
```
### Aspire doctor output
Aspire
⚠️ Aspire CLI version 13.5.0-preview.1.26376.5 (channel: daily) is out of date. Latest version is
13.5.0-preview.1.26378.1 (channel: prerelease)
Run 'aspire update' to update Aspire CLI.
✅ Developer Control Plane (DCP) connection health checks succeeded
.NET SDK
✅ .NET 10.0.302 installed (x64)
Container Runtime
✅ Docker v29.6.2: running (auto-detected (default)) ← active
Environment
✅ Operating system: Windows 10.0.26100.0
✅ HTTPS development certificate is trusted
Development Tools
✅ Aspire extension for VS Code is installed
Summary: 6 passed, 1 warnings, 0 failed
For detailed prerequisites: https://aka.ms/aspire-prerequisites
### Anything else?
I suspect this is a side effect of the changes to make `dotnet run` use the CLI. Probably needs to be reviewed prior to 13.5
Contributor guide
Assessment
This issue has not been assessed yet.