Skip to content

Conversation

@non124x124
Copy link
Contributor

Undocumented behaviour in ShellExecuteW:

If lpFile specifies an executable file and "open" or "runas" verbs are used in lpOperation, a whitespace character is appended to the commandline of the new created process.

If lpParameters is not null, the whitespace is added between the end of the executable name and lpParameters string in the commandline of the new created process.

Suggestion:

Document that ShellExecuteW appends a whitespace character to the commandline of the created process if lpFile specifies an executable file and open or runas verbs are used for lpOperation.

Undocumented behaviour in ShellExecuteW:

If lpFile specifies an executable file and "open" or "runas" verbs are used in lpOperation, a whitespace character is appended to the commandline of the new created process.
If lpParameters is not null, the whitespace is added between the end of the executable name and lpParameters string in the commandline of the new created process.

Suggestion:

Document that ShellExecuteW appends a whitespace character to the commandline of the created process if lpFile specifies an executable file and open or runas verbs are used for lpOperation.
@prmerger-automator
Copy link

@non124x124 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Document that the command line string of a process created with "open" or "runas" verbs specified in lpOperation includes a trailing whitespace character and if parameters are passed to the application with lpParameters, they are appended to that command line.
@jwmsft jwmsft merged commit 3f9a6c7 into MicrosoftDocs:docs Feb 28, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants