This PR backports the changes from #11951 to ensure consistent behavior between single-file and multi-file AppHost project runs in the Aspire CLI.

Changes

DotNetCliRunner.cs

• Single-file project support: Updated the single-file project run command to include the noProfileSwitch argument, aligning behavior with multi-file projects
• Improved argument handling: Changed from using the project file as a positional argument to using the --file flag for single-file projects
• Argument filtering: Added logic to filter out empty or whitespace-only arguments from the CLI args array, preventing invalid command-line arguments from being passed to dotnet run

Before:

true => ["run", projectFile.FullName, "--", ..args]

After:

true => ["run", noProfileSwitch, "--file", projectFile.FullName, "--", .. args]

And added:

cliArgs = [.. cliArgs.Where(arg => !string.IsNullOrWhiteSpace(arg))];

DotNetCliRunnerTests.cs

• Fixed indentation and removed trailing whitespace throughout the file
• Updated AddPackageAsyncUseFilesSwitchForSingleFileAppHost test to enable the SingleFileAppHostEnabled feature
• Added 3 new test methods:
  • RunAsyncAppliesNoLaunchProfileForSingleFileAppHost - Validates that --no-launch-profile is included when specified
  • RunAsyncDoesNotIncludeNoLaunchProfileForSingleFileAppHostWhenNotSpecified - Validates the flag is omitted when not specified
  • RunAsyncFiltersOutEmptyArgumentsForSingleFileAppHost - Validates that empty arguments are properly filtered out

Testing

All 386 CLI tests pass successfully with these changes, confirming no regressions were introduced.

Note

The original PR #11951 included additional tests that depend on features (Debug property, nonInteractiveSwitch, and verboseSwitch) not present in the target branch. This backport includes only the compatible changes while maintaining the core functionality improvements.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.