[WebToolsE2E][Aspire] Building a multi-target project from the App Host (e.g., .NET MAUI App with ".NET Aspire Orchestrator Support") fails with error MSB4057: The target "GetTargetPath" does not exist in the project.

[v-elenafeng]

REGRESSION INFO

Reproduces with VS 17.10 Preview 3 (Includes Aspire 8.0 P4) + Aspire 8.0 P5

INSTALL STEPS

Clean machine: Win11 x64 23h2 ENU

1. Install VS 17.10 Preview 3 from VS/main

   • Web Workload + Maui workload
   • Includes Aspire 8.0 Preview 4
   • Includes SDK 8.0.300-preview.24122.6

2. Create .NET MAUI App 8.0 and build

3. Right click the project > Add ".NET Aspire Orchestrator Support" > Build

ACTUAL
error MSB4057: The target "GetTargetPath" does not exist in the project.

This issue also reproduces with "Only Maui workload"

EXPECTED
The .NET MAUI App can be built successfully with ".NET Aspire Orchestrator Support".

[eerhardt]

I don't have MAUI installed locally. Can someone attach a binlog of the failing build, so we can see where it is coming from? That link has instructions on how to enable it for VS.

[eerhardt]

@v-elenafeng - the binlog at that location is for a build that succeeded. Can you grab the log for a build that fails with the above error?

[v-elenafeng]

@v-elenafeng - the binlog at that location is for a build that succeeded. Can you grab the log for a build that fails with the above error?

I grabbed the binlog after the build in VS showed a failure, but it wasn't captured in the logs, so I ran "dotnet build" the solution using CLI and the build was successful as well. So I will move this to DevOps since it's like a VS tooling issue.

Btw, I deleted the comment posted above since it's an internal shared path.

[BillHiebert]

Need to investigate this.

[BretJohnson]

Note that this issue looks to affect all multitargetted projects, not just MAUI. I created a Console app with <TargetFrameworks>net9.0;net8.0</TargetFrameworks> and saw the same The target "GetTargetPath" does not exist in the project error.

[v-elenafeng]

Yes, when adding '.NET Aspire Orchestrator Support' to a multi-target project, it keeps the AppHost single-targeted, so building the project throws an error. This can be fixed by modifying the AppHost project to be multi-targeted.

[BillHiebert]

I don't think multi-targeting AppHost is the right thing to do here. Since AppHost does not reference types from the referenced projects, I think it is better is to add the PrivateAssets="All" and ReferenceOutputAssembly="false" attributes to the project reference.