Aspire cli run commands should work without explicitly providing project file

[timdeschryver]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

First of all, congrats on the release! 🚀

It would be a small improvement to make the behavior of the aspire cli similar to dotnet cli.
With dotnet [command] --project we can provide it a directory, and it will discover the project file automatically.
This is not the case for aspire [command] --project, which expects the csproj file.

The following examples use the run command, but it's applicable to more commands, e.g. the publish command.

Using dotnet run it's possible to point to a directory:

dotnet run --project ./MyProject.AppHost

Using aspire run we're required to point it to a specific project file:

aspire run --project ./MyProject.AppHost/MyProject.AppHost.csproj

Expected Behavior

I expect running the following command automatically detects the project file.

aspire run --project ./MyProject.AppHost

Steps To Reproduce

No response

Exceptions (if any)

Running the command without project file results in the error:

The specified project file does not exist.

.NET Version info

.NET SDK:
Version: 9.0.203
Commit: dc7acfa194
Workload version: 9.0.200-manifests.528db46d
MSBuild version: 17.13.20+a4ef1e90f

Anything else?

No response

[davidfowl]

Fixed #8892