Exit error in Pipeline

Seems if you have "exit" in script and run it in NestedPipeline, you get an
error you can't catch and it bogs the shell. Example:

string runScript = "echo hello;exit";
Pipeline p = Runspace.DefaultRunspace.CreateNestedPipeline(runScript,
false);
using(p)
{
// Exception: Cannot exit nested prompt because no nested prompts exist.
Collection<PSObject> results = p.Invoke(inputArray); // <= Error
}

What gives?
--
William Stacey [C# MVP]

On Sep 7, 7:17 pm, "William Stacey [C# MVP]"
<william.sta...@xxxxxx> wrote: A nested prompt is a nested RUNSPACE, not a nested pipeline.

- Oisin

? I was not talking about a nested prompt. The code shows nested pipeline.
The question is if you have "exit" in the script, it will throw an error you
can not catch and also screws the runspace to boot.

--
William Stacey [C# MVP]



"Oisin Grehan" <oising@xxxxxx> wrote in message
news:1189288496.214391.75060@xxxxxx
| On Sep 7, 7:17 pm, "William Stacey [C# MVP]"
| <william.sta...@xxxxxx> wrote:
| > Seems if you have "exit" in script and run it in NestedPipeline, you get
an
| > error you can't catch and it bogs the shell. Example:
| >
| > string runScript = "echo hello;exit";
| > Pipeline p = Runspace.DefaultRunspace.CreateNestedPipeline(runScript,
| > false);
| > using(p)
| > {
| > // Exception: Cannot exit nested prompt because no nested prompts
exist.
| > Collection<PSObject> results = p.Invoke(inputArray); // <= Error
| >
| > }
| >
| > What gives?
| > --
| > William Stacey [C# MVP]
|
| A nested prompt is a nested RUNSPACE, not a nested pipeline.
|
| - Oisin
|

On Sep 8, 7:18 pm, "William Stacey [C# MVP]"
<william.sta...@xxxxxx> wrote: Ah I see what you mean. I thought you deliberately put the exit there,
expecting it to exit the nested pipeline (thus implying to me that you
were thinking runspaces). Anyway, that's weird. Out of interest, is it
_really_ a nested pipeline for the current runspace? (meaning there is
a parent pipeline in process)

- Oisin

right. The current pipeline is the currently executing pipeline (in this
case current pipeline of the psh runspace that started this cmdlet). So
this cmdlet starts a nestedpipeline (as we can't start a new pipeline
because one is already running) to run the script. I think they could
probably special case "exit" in this case and just do a "return" to avoid
the error.

--
William Stacey [C# MVP]


"Oisin Grehan" <oising@xxxxxx> wrote in message
news:1189302642.558959.176070@xxxxxx
| On Sep 8, 7:18 pm, "William Stacey [C# MVP]"
| <william.sta...@xxxxxx> wrote:
| > ? I was not talking about a nested prompt. The code shows nested
pipeline.
| > The question is if you have "exit" in the script, it will throw an error
you
| > can not catch and also screws the runspace to boot.
| >
| > --
| > William Stacey [C# MVP]
| >
| > "Oisin Grehan" <ois...@xxxxxx> wrote in message
| >
| > news:1189288496.214391.75060@xxxxxx
| > | On Sep 7, 7:17 pm, "William Stacey [C# MVP]"|
<william.sta...@xxxxxx> wrote:
| >
| > | > Seems if you have "exit" in script and run it in NestedPipeline, you
get
| > an
| > | > error you can't catch and it bogs the shell. Example:
| > | >
| > | > string runScript = "echo hello;exit";
| > | > Pipeline p =
Runspace.DefaultRunspace.CreateNestedPipeline(runScript,
| > | > false);
| > | > using(p)
| > | > {
| > | > // Exception: Cannot exit nested prompt because no nested
prompts
| > exist.
| > | > Collection<PSObject> results = p.Invoke(inputArray); // <= Error
| > | >
| > | > }
| > | >
| > | > What gives?
| > | > --
| > | > William Stacey [C# MVP]
| > |
| > | A nested prompt is a nested RUNSPACE, not a nested pipeline.
| > |
| > | - Oisin
| > |
|
| Ah I see what you mean. I thought you deliberately put the exit there,
| expecting it to exit the nested pipeline (thus implying to me that you
| were thinking runspaces). Anyway, that's weird. Out of interest, is it
| _really_ a nested pipeline for the current runspace? (meaning there is
| a parent pipeline in process)
|
| - Oisin
|