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

dotnet / aspire

An opinionated, cloud ready stack for building observable, production ready, distributed applications in .NET

https://learn.microsoft.com/dotnet/aspire

MIT License

3.65k stars 412 forks source link

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

Open hydra1102 opened 1 week ago

hydra1102 commented 1 week ago

Is there an existing issue for this?

[X] 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:

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

danegsta commented 1 week ago

@hydra1102 this looks like the same issue as https://github.com/dotnet/aspire/issues/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 commented 6 days ago

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

joperezr commented 5 days ago

Thanks for the report, @hydra1102. I have put up a PR https://github.com/dotnet/aspire/pull/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 commented 14 hours ago

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

OS version

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

kovacsandras2014 commented 1 hour ago

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