From 7eaf486d7257eabe118d8d79501cf4f15e0a428d Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 10 Apr 2026 13:27:11 +0000
Subject: [PATCH 1/5] Initial plan
From 14cfe6804eed3541b9bbd91dd3916bbd26c0d9f5 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 10 Apr 2026 13:31:50 +0000
Subject: [PATCH 2/5] docs: document the 'Use *.dev.localhost URLs?'
interactive prompt for aspire new
Agent-Logs-Url: https://github.com/microsoft/aspire.dev/sessions/49848864-c0a9-482c-a045-a860f76cb80f
Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
---
.../reference/cli/commands/aspire-new.mdx | 39 +++++++++++++++++++
1 file changed, 39 insertions(+)
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx
index 3de02172a..32dfc1ab1 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx
@@ -33,6 +33,45 @@ This command defaults to **interactive** mode. When executed without any options
with Aspire templates as an alternative for project creation.
+## Interactive prompts
+
+When running `aspire new` in interactive mode, the command asks one or more questions before generating the project. The available prompts depend on the template and options you provide.
+
+### Use \*.dev.localhost URLs?
+
+During project creation, you may be prompted:
+
+> **Use \*.dev.localhost URLs?**
+
+This prompt determines whether the generated launch profile configures your Aspire services to be accessible via `*.dev.localhost` wildcard subdomain URLs (for example, `https://myservice.dev.localhost`) instead of standard `http://localhost` with port numbers.
+
+#### What are \*.dev.localhost URLs?
+
+`*.dev.localhost` is a wildcard subdomain pattern that resolves to your local machine (`127.0.0.1` or `::1`) in all modern browsers—no DNS or hosts-file configuration is required. The ASP.NET Core HTTPS development certificate includes `*.dev.localhost` as a Subject Alternative Name (SAN), so browsers trust connections to any subdomain under `*.dev.localhost` when the certificate is installed and trusted.
+
+#### Yes — use \*.dev.localhost URLs
+
+Choosing **Yes** configures the generated project so that each service gets a unique subdomain URL such as `https://myservice.dev.localhost`. This option:
+
+- Enables HTTPS for all services from the start, leveraging the wildcard development certificate.
+- Gives each service its own origin, which prevents cookie and authentication token collisions between services running on the same machine.
+- More closely mirrors a production setup where services are hosted on separate (sub)domains.
+
+**Prerequisite:** The ASP.NET Core HTTPS development certificate must be installed and trusted on your machine. Run the following command if you haven't done so already:
+
+```bash
+dotnet dev-certs https --trust
+```
+
+
+
+#### No — use standard localhost URLs (default)
+
+Choosing **No** (the default) configures services with standard `http://localhost:` addresses. This option requires no certificate setup and works in all browsers and tools without additional configuration.
+
## Options
The following options are available:
From 2f96ae2b6587dfa808c25f6c357a94ab39ee1f99 Mon Sep 17 00:00:00 2001
From: David Pine
Date: Fri, 10 Apr 2026 14:57:54 -0500
Subject: [PATCH 3/5] Update aspire-new.mdx
---
.../src/content/docs/reference/cli/commands/aspire-new.mdx | 6 ------
1 file changed, 6 deletions(-)
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx
index 32dfc1ab1..ae331016c 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-new.mdx
@@ -57,12 +57,6 @@ Choosing **Yes** configures the generated project so that each service gets a un
- Gives each service its own origin, which prevents cookie and authentication token collisions between services running on the same machine.
- More closely mirrors a production setup where services are hosted on separate (sub)domains.
-**Prerequisite:** The ASP.NET Core HTTPS development certificate must be installed and trusted on your machine. Run the following command if you haven't done so already:
-
-```bash
-dotnet dev-certs https --trust
-```
-