Execute File still ignores configured command line shell

[huoshan12345]

The issue #84 was marked as fixed by commit fd6c471, but the problem still exists on my machine.

Expected behavior

When the command line is configured to use pwsh, all commands and script executions should use pwsh.

Actual behavior

Opening a terminal uses pwsh correctly, but executing a PowerShell script still launches Windows PowerShell (powershell.exe).

So currently there are still two different execution paths:

• Open terminal → respects configured shell
• Execute script → still uses Windows PowerShell

Environment

• Visual Studio 2026 18.6.0
• Open Command Line 2.6.14
• PowerShell 7.6.1 installed

[Smedis]

The actual bug is that .ps1 files are hard-coded to use "powershell.exe" for the "Execute File" action no matter what you have set in your options. Only the "Open Command Line" action is actually using your custom user settings.

This is a critical bug, since that forces it to ignore your user settings and execute the old and no-longer-supported PowerShell 5 ("powershell.exe"). The new, modern PowerShell is PowerShell 7 ("pwsh.exe").

See ExecuteFile() in OpenCommandLinePackage.cs:

            // Determine how to execute based on the configured command
            if (CommandLineLauncher.IsWindowsTerminal(command))
            {
                string execArgs;
                if (ext.Equals(".ps1", StringComparison.OrdinalIgnoreCase))
                    execArgs = $"{baseArgs} powershell.exe -ExecutionPolicy Bypass -NoExit -File \"{fileName}\"".Trim();
                else if (ext.Equals(".nu", StringComparison.OrdinalIgnoreCase))
                    execArgs = $"{baseArgs} nu.exe \"{fileName}\"".Trim();
                else
                    execArgs = $"{baseArgs} cmd.exe /k \"{fileName}\"".Trim();
                
                CommandLineLauncher.StartProcess(folder, command, execArgs, runAsAdmin);
            }
            else if (ext.Equals(".ps1", StringComparison.OrdinalIgnoreCase))
            {
                // PowerShell script - always use powershell.exe
                CommandLineLauncher.StartProcess(folder, "powershell.exe", $"-ExecutionPolicy Bypass -NoExit -File \"{fileName}\"", runAsAdmin);
            }

It think that code to be changed to something like this:

            else if (ext.Equals(".ps1", StringComparison.OrdinalIgnoreCase))
            {
                // Pull the exact executable the user selected in the preset
                string command = Options.Instance.Command;

                // Pull the exact arguments the user selected in the preset (e.g., "-NoExit")
                string baseArgs = Options.Instance.CommandArguments;

                // Append the file parameter so the shell knows what script to run
                string arguments = $"{baseArgs} -File \"{fileName}\"";

                // Launch using strictly the user's configured environment
                CommandLineLauncher.StartProcess(folder, command, arguments, runAsAdmin);
            }

This way it should use whatever the user has selected in his current preset for the "Command" as well as the "Command arguments", as-is. This pushes the decision of how to format the command arguments to the user. Currently, the code tries to fix the arguments for them if the user has selected to launch processes within Windows Terminal ("wt"), but when doing so, it completely ignores the "Command" and "Command arguments" user settings.