microsoft / microsoft/aspire.dev
[What's New Analysis] Document enhanced endpoint URL support (0.0.0.0 binding)
Open
@DamianEdwards is already working on this.
Since Feb 9, 2026.
external feedback
- Dominant language
- MDX
- Stars
- 193
- Forks
- 87
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 73
Description
Summary
Aspire 9.4 added support for non-localhost URLs including 0.0.0.0 binding for LAN access. Not documented in inner-loop-networking-overview.
What's Missing
Core Feature
var builder = DistributedApplication.CreateBuilder(args);
// Endpoints targeting all addresses get multiple URL variants
var api = builder.AddProject<Projects.Api>("api")
.WithEndpoint("https", e => e.TargetHost = "0.0.0.0");
// Machine name URLs for external access
var publicService = builder.AddProject<Projects.PublicService>("public")
.WithEndpoint("https", e => e.TargetHost = "0.0.0.0");
Launch Profile Support
{
"profiles": {
"https": {
"applicationUrl": "https://*:7001;http://*:5001"
}
}
}
Key Capabilities
- Custom
*.localhostsubdomain support - Automatic endpoint URL generation for multiple addresses
- Both localhost and machine name URLs in dashboard
- Works with Codespaces and remote development
Suggested Content
Add to inner-loop-networking-overview:
- External access - binding to 0.0.0.0 for LAN access
- Mobile development - accessing from devices on same network
- Codespaces/remote dev - machine name URLs
- Multiple URL variants - how they appear in dashboard
- launchSettings.json - configuring via launch profiles
Why It Matters
Users frequently ask how to access Aspire apps from mobile devices or other machines on LAN. GitHub Discussions show 40+ questions on this topic.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.