Skip to content
This repository was archived by the owner on Jun 5, 2025. It is now read-only.
This repository was archived by the owner on Jun 5, 2025. It is now read-only.

[External Tools] Make the external tools command-line composition more open-ended #3082

@andreww-msft

Description

@andreww-msft

Suggested new feature or improvement

Our existing command-line composition is somewhat primitive, and is an opportunity for some more sophisticated design. Some things to consider:

  1. It assumes blank spaces between switches/params. Some apps don't like a space (eg /s:123 as opposed to /s 123).
  2. We only support PID and HWND parameters. Consider process name, executable path, aumid, window title.
  3. We should probably allow the user to type in a command-line - this way its completely open-ended and not constrained to our notion of a command-line. If we do this, we'd want to support named variable substitutions, something like: /abc /foo /p{pid} /w{hwnd}.

Scenario

As part of this, we also need to support other activation mechanisms beyond command-line args. For example, protocol activation, appExecutionAlias, file-type association.

Additional details

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions