GenerateAssemblyInfo must be true else "Property CliPath: The path to the DCP executable used for Aspire orchestration is required"

[to-mas-kral]

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]

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

[joperezr]

@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 #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]

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

[lnaie]

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]

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

[Garwin4j]

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

This worked for me.

[NinjaCross]

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

Is there a way to signal to the developer this kind of requirement ?
(I mean the fact that GenerateAssemblyInfo must be true).
I couldn't find it in the docs, I had no warnings during the build, and it made my life miserable for a good 4 hours, before I discovered the problem by mere chance.

[DamianEdwards]

Let's just update our targets to log a build error if GenerateAssemblyInfo is disabled.

[sven-n]

Please add something to the documentation and to the build output. I wasted several hours on this, until I noticed that the generated AssemblyInfo contains the required paths...