Powershell script changes directory of parent powershell

Question

When running a powershell script which changes a directory via cd (or set-location/push-location/etc.), the console that the script was run from also ends up in that directory.

Example: script.ps1

cd c:\tmp
# do stuff

If I run this from c:\users\me, i end up in c:\tmp.

PS C:\users\me> .\script.ps1
PS C:\tmp> |

Now I know that I could use push-location and later do pop-location. However this wouldn't work if the script stopped somewhere in the middle (via Exit).

How can I solve this? Why doesn't the script have it's own location stack?

You could always use Try/Catch/Finally. Set the current directory path to a variable and then cd c:\tmp before the Try, and have the directory changed to variable in the Finally? — JClaspill
– JClaspill, Commented Dec 17, 2014 at 16:03
thx, @arco444. However this only works if the script location is known, I get a problem if it's somewhere on $env:PATH. — Igor Lankin
– Igor Lankin, Commented Dec 17, 2014 at 16:10
@IgorLankin What...? What do you mean if the script location is known? From your example you seem to know where it is... — arco444
– arco444, Commented Dec 17, 2014 at 16:11

JClaspill · Accepted Answer · 2014-12-17 16:42:37Z

2

You could always use Try/Catch/Finally. Set the current directory path to a variable and then cd c:\tmp before the Try, and have the directory changed to variable in the Finally?

Example 1

$path = (Get-Item -Path ".\" -Verbose).FullName
cd c:\temp
Try
{
    #Do stuff
    #exit is fine to use
    #this will output the directory it is in, just to show you it works
    Write-Host (Get-Item -Path ".\" -Verbose).FullName
}
Catch [system.exception]
{
    #error logging
}
Finally
{
    cd $path
}

Example 2 using popd and pushd

pushd c:\temp
Try
{
    #Do stuff
    #exit is fine to use
    #this will output the directory it is in, just to show you it works
    Write-Host (Get-Item -Path ".\" -Verbose).FullName
}
Catch [system.exception]
{
    #error logging
}
Finally
{
    popd
}

I'd also recommend looking at what arco444 suggested, which is calling the powershell script via the -File parameter. Depending on the scenario that might work as an option.

edited Dec 17, 2014 at 16:42

answered Dec 17, 2014 at 16:12

JClaspill

1,74519 silver badges30 bronze badges

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

3 Comments

Igor Lankin Over a year ago

Thank you. This solves the issue. I still think the script should have its own location stack, though.

Igor Lankin Over a year ago

I'd prefer pushd c:\tempand just popd in the finally block. The commands are available since PS 2.0. See technet.microsoft.com/en-us/library/hh849855.aspx

JClaspill Over a year ago

@IgorLankin Added the pushd example for any future viewers. Good stuff!

Collectives™ on Stack Overflow

Powershell script changes directory of parent powershell

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related