Accessing variables defined in a scriptblock after running Invoke-Command

Question

I'll try to make this example as simple as possible.

$myValues = {
    $value1 = "hello"
    $value2 = "world"
}

Invoke-Command $myValues

How can I access $value1 and $value2 after the Invoke-Command executes?

Edit: The problem I am trying to solve is that I will have to initialize the variables within $myValues multiple times throughout my script. So I figured I would define the scriptblock ONCE at the top and then simply call Invoke-Command on $myVariables whenever I need to reinitialize the variables.

You don't unless you return them from the command. It's literally the first line in the help document: The Invoke-Command cmdlet runs commands on a local or remote computer and returns all output from the commands — Maximilian Burszley
– Maximilian Burszley, Commented Jan 10, 2018 at 22:33
Please take a step back and describe the actual problem you're trying to solve instead of what you perceive as the solution. What do you think you need this for? — Ansgar Wiechers
– Ansgar Wiechers, Commented Jan 10, 2018 at 22:40

Mike Shepard · Accepted Answer · 2018-01-10 22:57:56Z

6

If you dot-source the scriptblock it will run in your current scope and the variables will be available afterwards.

$myValues = { 
    $value1 = "hello"
    $value2 ="world"
}

. $myValues

answered Jan 10, 2018 at 22:57

Mike Shepard

18.4k7 gold badges58 silver badges72 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Eric Furspan Over a year ago

THIS! exactly what I needed. Thank you

B3W · Accepted Answer · 2018-01-10 22:55:25Z

Return both values in the scriptblock and assign a variable to your invoke-command. You can then access the variables from the returned array:

$myValues = { 
    $value1 = "hello"
    $value2 ="world"
    $value1
    $value2
}

$remoteOutput = Invoke-Command $myValues
$remoteOutput[0]
$remoteOutput[1]

The output as tested on my computer will be:

hello
world

Let me know if this solves the problem you are having. If not we can work toward a different solution!

Ansgar Wiechers · Accepted Answer · 2018-01-10 22:58:11Z

0

A requirement to frequently re-initialize variables usually indicates poor design. With that said, if for some reason you still must do that I'd use a function to (re-)initialize the variable set in the global or script scope:

function Initialize-VariableSet {
    $script:value1 = 'hello'
    $script:value2 = 'world'
}

Demonstration:

PS C:\> Initialize-VariableSet
PS C:\> $value1
hello
PS C:\> $value1 = 'foobar'
PS C:\> $value1
foobar
PS C:\> Initialize-VariableSet
PS C:\> $value1
hello

answered Jan 10, 2018 at 22:58

Ansgar Wiechers

201k27 gold badges286 silver badges363 bronze badges

1 Comment

Eric Furspan Over a year ago

Won't get into the complex reason why I need to re-init the vars but its a good enough reason and ill leave it at that. Thanks for the reply!

Collectives™ on Stack Overflow

Accessing variables defined in a scriptblock after running Invoke-Command

3 Answers 3

1 Comment

Comments

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

1 Comment

Related