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 Aaspire orchestration is required; Property DashboardPath: The path to the Aspire Dashboard binaries is missing #5674

Closed
1 task done
hydra1102 opened this issue Sep 10, 2024 · 8 comments · Fixed by #5695

Comments

@hydra1102
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

accrording to https://learn.microsoft.com/en-us/dotnet/aspire/get-started/build-your-first-aspire-app?pivots=dotnet-cli
1st dotnet new aspire-starter --use-redis-cache --output AspireSample
2nd modify the csproj file
3rd dotnet restore and succeeded
4th donet build and succeeded
5th dotnet run --project AspireSample/AspireSample.AppHost

when i run 5th step,the error occured:
Property CliPath: the path to the dcp executable used for Aaspire orchestration is required; Property DashboardPath: The path to the Aspire Dashboard binaries is missing

Expected Behavior

how can i fix the problem and run normally

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

4444

Anything else?

the log content:
111

when 2nd step i write the aspire1.AppHost.csproj file content:
3333

@danegsta
Copy link
Member

@hydra1102 this looks like the same issue as #5486; you'll likely need to update your SDK to a newer version than 8.0.100. Other Fedora/RHEL users are reporting that installing SDK 8.0.401 works to unblock them. Basically, the build targets are expecting linux-x64 for the SDK architecture, but with 8.0.100 some distros are reporting custom architecture values for the check we make (i.e. fedora-x64 or rhel-x64 instead of linux-x64).

@hydra1102
Copy link
Author

@danegsta thanks. I have installed the sdk 8.0.401 by script, and run the aspire-starter succeeded

@joperezr
Copy link
Member

Thanks for the report, @hydra1102. I have put up a PR #5695 that will fix this issue and you'll be able to remove the manual workarounds and won't need to pin to an older workload any longer.

@kovacsandras2014
Copy link

Hello, I have the same issue on Ubuntu 22.04. Having upgraded Aspire to 8.2 and modified my AppHost.csproj as above, I got the same error. Upgrading to SDK 8.0.401 didn't help.

.NET version and workloads
image

OS version
image

Any idea or workaround how can I get my project to run?

@kovacsandras2014
Copy link

Uninstall/reinstall Aspire workload, clean and rebuild the solution has solved the problem.

@DclearEE
Copy link

DclearEE commented Oct 2, 2024

Uninstall/reinstall Aspire workload, clean and rebuild the solution has solved the problem.

This worked for me. For anyone using the CLI the commands are
dotnet workload uninstall aspire
dotnet workload install aspire

@snuup
Copy link

snuup commented Oct 30, 2024

the same problem and nothing of the above helped. please repoen this.

@joperezr
Copy link
Member

joperezr commented Nov 1, 2024

@snuup can you please run dotnet workload update --print-rollback and paste the output you get?

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