Named endpoints (13.2 breaking changes)

@IEvangelist is already working on this.

Since Jun 2, 2026.

Can someone please explain to me how named endpoints works?

It looks like there is some confusion in the docs...

[service-discovery-environment-variable-naming](https://aspire.dev/whats-new/aspire-13-2/#service-discovery-environment-variable-naming)

[named-endpoint-doesnt-resolve](https://aspire.dev/fundamentals/service-discovery/#named-endpoint-doesnt-resolve)

I have tried to create a aspire starter project and just added a HTTP dashboard endpoint on port 9999 in the apphost.

```csharp
var builder = DistributedApplication.CreateBuilder(args);

var apiService = builder.AddProject("apiservice")
.WithHttpEndpoint(9999, name: "dashboard")
.WithHttpHealthCheck("/health");

builder.AddProject("webfrontend")
.WithExternalHttpEndpoints()
.WithHttpHealthCheck("/health")
.WithReference(apiService)
.WaitFor(apiService);

builder.Build().Run();
```

And then set the BaseAddress of an httpclient in the webfrontend project.

```csharp
builder.Services.AddHttpClient(client =>
{
client.BaseAddress = new("http://_dashboard.apiservice");
});
```

But I still get System.Net.Http.HttpRequestException: No such host is known. (apiservice:80) ---> System.Net.Sockets.SocketException (11001): No such host is known.

---

Update!

It might be working now after this commit

https://github.com/microsoft/aspire/commit/efcd138e8bfda89501b1f7292485571d8acdd9ae#diff-19fa606291a5a92010a16a21c80f5b0e0f7f6f76b97fa755cf30930f6b594188