Please add .shell-like functionality to the Debugger Data Model

[JamesMcNellis]

I have a JavaScript debugger extension. From it, I would like to start another program.

Currently, I am using ExecuteCommand to run .shell to start the program. This mostly works. However, if the program runs for more than ten seconds, the debugger gets "stuck," with the command window waiting for "Input>".

Repro Steps:

1. Create a new JavaScript imperative extension with the following contents:

"use strict";

function initializeScript()
{
    return [new host.apiVersionSupport(1, 9)];
}

function invokeScript()
{
    host.namespace.Debugger.Utility.Control.ExecuteCommand('.shell -ci "*" powershell -Command "Start-Sleep -Seconds 15"');
}

2. Run the script
3. Wait 15 seconds

Observe that the debugger is now stuck waiting for input.

If we run the .shell directly in the command window, we can see what the problem is:

0:022> .shell -ci "*" powershell -Command "Start-Sleep -Seconds 15"
<.shell waiting 10 second(s) for process>
<.shell running: .shell_quit to abandon, ENTER to wait>.shell: Process exited

However, when running the command from a script, the output from .shell is not printed to the command window so there is no indication as to why things are stuck.

It would be nice if the Debugger Data Model just exposed something similar to ExecuteCommand that can be used to run another program.