[Discord Feedback] App Model API gaps - CORS, console apps, naming, networking

Summary

Based on analysis of 20,415 Discord messages + 147 #help threads from the Aspire community (April 2025 - February 2026), several App Model API features lack documentation.

Missing Documentation

1. CORS Configuration (10+ questions)

Current State: Zero documentation

Customer Quotes:

"Wait.. hold on, hold on, hold on, hold on, hold on.... What? do we need to configure cors?"

"I seem to be having some CORS issues with a test deployment. Would this also have to be something I configure somewhere in my project?"

Requested Documentation:

• When CORS configuration is needed with Aspire
• How to configure CORS for dev vs prod
• Common CORS issues and solutions

---

2. Console Application Integration (17 questions)

Customer Quotes:

"if I want to hook up a Console project with Aspire, so that it can still (maybe?) use service discovery, service defaults, etc. with Aspire resources... is that possible?"

"Colleague asked how to start a console app with aspire. I got it to connect to another resource (redis) and write a kv.... but then was wondering how to 'launch the console window' so one could interact with Console.Readline."

Requested Documentation:

• Adding Console apps to Aspire AppHost
• Service discovery in Console apps (non-ASP.NET Core)
• Background worker / hosted service patterns
• Interactive console apps with stdin/stdout

---

3. Resource Naming Conventions

Customer Quote:

"How does WithReference treat names that have dashes? e.g. AddWhatever("my-service") and then will it be like MY_SERVICE_[PROPERTY]? Or MY-SERVICE_[PROPERTY]?"

Requested Documentation:

• How resource names map to environment variables
• Dashes → underscores transformation rules
• Best practices for naming resources

---

4. Network Binding (0.0.0.0 / LAN Access)

From #help thread: "How to bind services to 0.0.0.0 for LAN access?"

Requested Documentation:

• Exposing services to external network
• Binding to 0.0.0.0 vs localhost
• LAN development scenarios

---

5. Container-to-Host Networking

Customer Quote:

"I'm struggling to get endpoints resolved in the context of a container. If I use KnownNetworkIdentifiers.LocalhostNetwork, it always comes back with localhost not host.docker.internal"

From #help: "Containers can't reach localhost SQL"

Requested Documentation:

• host.docker.internal behavior
• KnownNetworkIdentifiers enum usage
• Container-to-localhost SQL Server connectivity

---

Data Source

• Discord channels: #💫│general, #🔵│azure, #🔨│building-resources
• Help threads: 147 analyzed from #🆘│help
• Total messages: 20,415
• Date range: April 2025 - February 2026