Allow `dotnet run` to use launch profiles with `commandName: Executable`

[TacoConKvass]

This is a disparity between the dotnet CLI and Visual Studio.
I was trying to use the dotnet CLI for running a 3rd party application, specified in launchSettings.json, which my project is a plugin for, however, the "Executable" type is not supported. It does however work with Visual studio.

Describe the solution you'd like

Allow dotnet run to launch the 3rd party application and possibly take control of it's life cycle in some way so that hot reload can work with dotnet watch.

[marcpopMSFT]

Triage: VS has a few different launch targets we don't support currently. There is a similar ask for container support. Moving to backlog as we collect more feedback.

[DragonDev1906]

Are there any workarounds for this (for example by starting the 3rd party dll manually in a separate terminal)?
In my case the 3rd party application is available as a dll and not just an executable (if that makes a difference)

[baronfel]

No workaround as of yet, but the Project System team has docs about their profiles and how they are supported here. We'd need someone to contribute the handling for the "executable" type, as we're working on other things at this time. If you wanted to do that, we'd gladly help you get a PR merged!