Add user-friendly error handling for aspire new when directory contains existing files

[Copilot]

Summary

Fixes #9685 by replacing the long, unfriendly error output from dotnet new with a clear, actionable message when users attempt to create a new Aspire project in a directory that already contains files.

Problem

When running aspire new in a directory that already contains files from a previous project, the command would fail with exit code 73 and display a long, technical error message from dotnet new that mentioned the unsupported --force option. This was confusing for users since the aspire CLI doesn't support the --force flag.

Before:

Creating this template will make changes to existing files:
  Overwrite   Program.cs

To create the template anyway, run the command with '--force' option:
   dotnet new console --name TestConsole2 --output . --force

For details on the exit code, refer to https://aka.ms/templating-exit-codes#73

Solution

Added custom error handling that detects exit code 73 from dotnet new and displays a user-friendly message instead.

After:

The output folder already contains files from a previous project. Please remove or move these files before creating a new project in this location.

Changes Made

Core Implementation

• Added ProjectAlreadyExistsException: New custom exception in Aspire.Cli.Exceptions namespace
• Enhanced DotNetCliRunner.NewProjectAsync: Modified to detect exit code 73 from dotnet new and throw the custom exception with reference to issue aspire new asks you to use --force on dotnet new if the folder already exists. #9685
• Enhanced DotNetTemplateFactory.ApplyTemplateAsync: Added try-catch block to handle ProjectAlreadyExistsException and display the user-friendly error message

Resources

• Added resource string: New ProjectAlreadyExists string in TemplatingStrings.resx with the user-friendly message
• Updated Designer.cs: Added corresponding property for the new resource string

Testing

• Added end-to-end test: NewCommandWithExitCode73ShowsUserFriendlyError verifies the complete flow returns the correct exit code
• Added unit test: NewProjectAsyncThrowsProjectAlreadyExistsExceptionOnExitCode73 verifies DotNetCliRunner throws the correct exception on exit code 73
• All 112 CLI tests pass: No regressions introduced

Technical Details

The implementation is surgical and minimal:

1. Detection: DotNetCliRunner.NewProjectAsync checks if dotnet new returns exit code 73
2. Exception: Throws ProjectAlreadyExistsException instead of returning the exit code
3. Handling: DotNetTemplateFactory.ApplyTemplateAsync catches the exception and displays the friendly message
4. Fallback: All other exit codes continue to work exactly as before

Verification

✅ Functionality verified: Confirmed dotnet new returns exit code 73 when attempting to create templates in directories with existing files
✅ No regressions: All existing CLI functionality preserved
✅ Error handling: Custom exception properly thrown and caught
✅ User experience: Clear, actionable error message displayed

The change provides users with clear guidance on how to resolve the issue (remove or move existing files) without mentioning unsupported options.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• go.microsoft.com

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

This pull request was created as a result of the following prompt from Copilot chat.

Currently, when running 'aspire new' in a directory that already contains files from a previous project, the command fails because 'dotnet new' returns exit code 73. The error output shown to users is long and includes a mention of the unsupported '--force' option. We want to improve this by detecting exit code 73 and instead displaying a user-friendly error that does not mention '--force'. The message should advise users to remove or move existing files before creating a new project.

Requirements:

• In the code that executes 'dotnet new' (via IDotNetCliRunner in NewCommand or related templating logic), detect if the exit code is 73.
• If exit code 73 is detected, throw a custom exception (e.g., ProjectAlreadyExistsException).
• Catch this exception where user-facing messages are rendered, and show:
  "The output folder already contains files from a previous project. Please remove or move these files before creating a new project in this location."
• Do not mention '--force' in the error message, since it's not supported by the aspire CLI.
• Reference issue aspire new asks you to use --force on dotnet new if the folder already exists. #9685 in the PR.

Context:

• This is to replace the long, unfriendly error output from 'dotnet new' when duplicate project creation is attempted.
• The goal is to provide clearer, actionable guidance to users.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[mitchdenny]

Here is a screenshot of the output that this code produces for reference:

@copilot you can ignore this comment - no action is necessary.

[mitchdenny]

LGTM @davidfowl @maddymontaquila I think this one is ready to go in (also needs to be backported).

[davidfowl]

It turns out dotnet new works fine if you put multiple projects in the same folder as long as there are no conflicts:

Maybe we update the error message to reflect that. Otherwise this looks good.

[Copilot]

It turns out dotnet new works fine if you put multiple projects in the same folder as long as there are no conflicts:

<img width="2574" height="952" alt="image" src="https://github.com/user-attachm...

Updated the error message to be more accurate - it now clarifies that the issue is specifically about conflicting files that would be overwritten, not just any existing files in the directory. See commit 76fe7af.

[davidfowl]

/backport to release/9.4

[github-actions]

Started backporting to release/9.4: https://github.com/dotnet/aspire/actions/runs/16383156860