Reuben Bond

Superseded by #8881. Thanks again for the fix, @ccorsano!

Your hypothesis sounds right. Taking a look

The relevant line is [here](https://github.com/dotnet/aspire/blob/40a1675a45c2c86e82e3829801f114ce339047cf/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs#L947), but it already looks correct to me: we are accounting for non-proxied ports by no-op'ing. I wonder what's going wrong in this case. My guess...

Yep, that's it. If I specify a launch profile in the sample, it works: ```csharp var builder = DistributedApplication.CreateBuilder(args); builder.AddRedis("redis1"); builder.AddProject("mywebapp1", "https") // Specify "https" to make it work .WithEndpoint("http",...

> Hmm if we aren't loading launch settings how does it get endpoints at all? Or do you mean we simply ignore the ports specified in the launch settings when...

Hi @bit365, could you please elaborate on what isn't working? When you debug the tests, what do you see? The env vars for service discovery ought to be getting injected....

@bit365 it is not clear what the issue is yet. My hunch is that it could be related to launch profiles. Could you show the launchSettings.json files for your projects?

This can be useful. We added something similar in the Aspire.Hosting.Testing package as an extension on DistributedApplication. The API would need to take an optional endpoint name. I would prefer...

I am hitting this issue when testing the preview Cosmos DB emulator with Orleans

@kengiczhangchao there is no response for a timer execution, so there would be nothing to catch the exception. This is true for timers in .NET in general: there is no...