Eric Erhardt

If you aren't pushing the final image to another store, wouldn't copying the final assets into ANOTHER image "balloon the image store" more than necessary?

No. Not yet

> I still have this problem [#6432 (comment)](https://github.com/dotnet/aspire/pull/6432#issuecomment-2429935302) @eerhardt can you help me fix that? From the root of your repo, run the following and ensure you get the same...

We should be able to remove these 2 lines now, right? https://github.com/dotnet/aspire/blob/232e434c79acd2bd1221ad05a5d2dd5118018804/tests/Aspire.Hosting.Tests/Aspire.Hosting.Tests.csproj#L21 https://github.com/dotnet/aspire/blob/232e434c79acd2bd1221ad05a5d2dd5118018804/tests/Aspire.Hosting.Tests/Aspire.Hosting.Tests.csproj#L28

This is now fixed with the latest nightly build (using Azure.Provisioning v1.0.1). One note is that the CPU and Memory configuration needs to match an available config in ACA. So...

There are 2 cases where PublishSingleFile helps: 1. The size on disk will generally be smaller. I can't remember exactly why, but maybe @vitek-karas or @sbomer know why. I thought...

This is also supported on .NET projects/CSharpApps - [Add ContainerFilesDestinationAnnotation support to ProjectResource (dotnet/aspire#12355)](https://github.com/dotnet/aspire/pull/12355) And on Yarp - [Refactor YarpResource and add PublishWithStaticFiles method for Dockerfile (dotnet/aspire#12483)](https://github.com/dotnet/aspire/pull/12483)

@DamianEdwards - do you think this is necessary for 8.0? With the generator, the starting path is provided in the assembly level attribute: https://github.com/dotnet/aspire/blob/fc1dd495456cea3c1b0cf583c05fd18e3052a3f2/src/Components/Aspire.StackExchange.Redis/AssemblyInfo.cs#L8-L9 We can have a set of...

This doesn't seem like a ship-stopping issue. Moving to `8.1`.

This is going to need https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/pull/2266. See https://github.com/dotnet/aspire/pull/5120#discussion_r1699200942.