Run script within push and pop location

Summary of the new feature / enhancement

As a user, I want to be able to execute code in a different directory so that I can quickly run a command and return to my current state.

Having a single command for this removes the need for wrapping these commands in pushd and popd

I am unaware of this functionality existing elsewhere, although the only place I could think of was Invoke-Command

Proposed technical implementation details (optional)

This can be achieved with the following script:

function Use-Location {
  [CmdletBinding()] param (
    [Parameter(Mandatory)] [string] $Location,
    [Parameter(Mandatory)] [scriptblock] $ScriptBlock
  )
  Push-Location -Path $Location
  Invoke-Command -ScriptBlock $ScriptBlock
  Pop-Location
}

Example usage:

"repo1/my-project", "repo2/my-other-project" | %{
  Use-Location $_ {dotnet build}
}

[aguzev]

This improvement could cover the risk of unpaired Push-Location calls in the invoked script block, mentioned by @fflaten above.

An alternative implementation.

Invoke-Command -WorkingDirectory '… a path …" -ScriptBlock { … }

"repo1/my-project", "repo2/my-other-project" | %{
  Invoke-Command -WorkingDirectory $_ {dotnet build}
}

[MattMS]

Thank you for the feedback about the missing Pop-Location issue, and especially for the multiple suggested solutions, that is helpful.

My request was prompted after writing a loop for building and publishing packages:

Get-ChildItem src | % {
  Push-Location $_
  dotnet build
  Push-Location bin/Release
  dotnet nuget push *.nupkg
  Pop-Location
  Pop-Location
}

I thought it would be cleaner if I could do the following instead:

Get-ChildItem src | % {
  Use-Location $_ {dotnet build}
  Use-Location $_/bin/Release {dotnet nuget push *.nupkg}
}

As this is intended to be committed in a repo, it would not work having this function only defined in my profile.