Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Property CliPath: The path to the DCP executable used for Aspire orchestration is required #506

Open
to-mas-kral opened this issue Oct 9, 2024 · 5 comments

Comments

@to-mas-kral
Copy link

When I try to run any of the samples, I get this error:
System.AggregateException: One or more errors occurred. (Property CliPath: The path to the DCP executable used for Aspire orchestration is required.; Property DashboardPath: The path to the Aspire Dashboard binaries is missing.)

I have installed the Aspire workload. I'm on ArchLinux with dotnet-sdk 108.

Interestingly, creating a sample with dotnet new aspire-starter --use-redis-cache --output AspireSample and running it with dotnet-run does work.

@DamianEdwards
Copy link
Member

@karelz @joperezr @danegsta any idea on this one?

@joperezr
Copy link
Member

joperezr commented Nov 6, 2024

@to-mas-kral sorry for not seeing this sooner, and than you for logging the issue. Since this is an older issue, I believe it could just be a dupe of dotnet/aspire#5674 which has already been fixed. Can you make sure that you are on the latest version of the workload by running dotnet workload update to get a version that has the fix?

@baoduy
Copy link

baoduy commented Nov 25, 2024

I tried Aspire 9 today and still got this error when running Aspire XUnit Test

@lnaie
Copy link

lnaie commented Nov 30, 2024

I have a non-flat structure of the Aspire project, on Windows 11. I like that setup.
Also I wanted to make use of the setting:
<GenerateAssemblyInfo>false</GenerateAssemblyInfo>
in all my csproj files (because I want to use my own AssemblyInfo.cs), but it breaks the runtime with the same error, when I use it in AppHost csproj.

Is this known?
Is there a workaround for it, except not using it only in AppHost.csproj?

@davidfowl
Copy link
Member

No there’s no workaround. Enable it in the apphost project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants