aspire: commandLineArgs not working when adding a project with a launchProfileName
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
When adding a project, and specifying a launchProfileName the correct launch profile is used. However the commandLineArgs of the launch profile are not being passed on during execution.
Expected Behavior
The commandLineArgs are passed through as the arguments when the project is run.
Steps To Reproduce
https://github.com/distantcam/AspireLaunchArgsIssue
Run the apphost, notice the prestart resource doesn’t finish, blocking the start of the main resource.
Exceptions (if any)
No response
.NET Version info
No response
Anything else?
This was working in the previous version of Aspire (8.0).
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 18 (12 by maintainers)
@LittleLittleCloud if this is fixed, lets close it.
Thanks @LittleLittleCloud
Regardless what you find, there should be no case where a project quitting “very fast” is causing issues. If there is a timing issue in the current implementation, we have to find and fix it. E.g. in the past I have been working with @tlmii to properly handle the case where project termination notification arrives before the request to start THAT VERY PROJECT completes.
Sorry I meant @LittleLittleCloud 😄
Reproduces in visual studio. @bradygaster @JakeRadMSFT can you take a look at this one. That inconsistent behavior is a problem.