这个函数将提示位置设置为脚本路径，处理vscode, psise和PWD之间获取脚本路径的不同方式:

function Set-CurrentLocation
{
    $currentPath = $PSScriptRoot                                                                                                     # AzureDevOps, Powershell
    if (!$currentPath) { $currentPath = Split-Path $pseditor.GetEditorContext().CurrentFile.Path -ErrorAction SilentlyContinue }     # VSCode
    if (!$currentPath) { $currentPath = Split-Path $psISE.CurrentFile.FullPath -ErrorAction SilentlyContinue }                       # PsISE

    if ($currentPath) { Set-Location $currentPath }
}

I had similar problems and it made me a lot of trouble since I am making programs written in PowerShell (full end user GUI applications) and I have a lot of files and resources I need to load from disk. From my experience, using . to represent current directory is unreliable. It should represent current working directory, but it often does not. It appears that PowerShell saves location from which PowerShell has been invoked inside .. To be more precise, when PowerShell is first started, it starts, by default, inside your home user directory. That is usually directory of your user account, something like C:\USERS\YOUR USER NAME. After that, PowerShell changes directory to either directory from which you invoked it, or to directory where script you are executing is located before either presenting you with PowerShell prompt or running the script. But that happens after PowerShell app itself originally starts inside your home user directory.

And . represents that initial directory inside which PowerShell started. So . only represents current directory in case if you invoked PowerShell from the wanted directory. If you later change directory in PowerShell code, change appears not to be reflected inside . in every case. In some cases . represents current working directory, and in others directory from which PowerShell (itself, not the script) has been invoked, what can lead to inconsistent results. For this reason I use invoker script. PowerShell script with single command inside: POWERSHELL. That will ensure that PowerShell is invoked from the wanted directory and thus make . represent current directory. But it only works if you do not change directory later in PowerShell code. In case of a script, I use invoker script which is similar to last one I mentioned, except it contains a file option: POWERSHELL -FILE DRIVE:\PATH\SCRIPT NAME.PS1. That ensures that PowerShell is started inside current working directory.

只需单击脚本就可以从主用户目录调用PowerShell，而不管脚本位于何处。 它的结果是当前工作目录是脚本所在的目录，但PowerShell调用目录是C:\USERS\YOUR USER NAME，与。根据情况返回这两个目录中的一个，这是荒谬的。

但是为了避免所有这些麻烦并使用调用程序脚本，您可以简单地使用$PWD或$PSSCRIPTROOT来代替。表示当前目录，具体取决于您希望表示当前工作目录还是已从其中调用脚本的目录。 如果你出于某种原因，想要检索两个目录中的另一个。返回时，您可以使用$HOME。

就我个人而言，我用PowerShell开发的应用程序的根目录中只有调用程序脚本，它会调用我的主应用程序脚本，只要记住永远不要改变应用程序源代码中的当前工作目录，所以我永远不必担心这个问题，我可以使用。要表示当前目录和支持相对文件寻址在我的应用程序没有任何问题。 这应该适用于PowerShell的新版本(更新于版本2)。

Path通常为空。这个功能比较安全。

function Get-ScriptDirectory
{
    $Invocation = (Get-Variable MyInvocation -Scope 1).Value;
    if($Invocation.PSScriptRoot)
    {
        $Invocation.PSScriptRoot;
    }
    Elseif($Invocation.MyCommand.Path)
    {
        Split-Path $Invocation.MyCommand.Path
    }
    else
    {
        $Invocation.InvocationName.Substring(0,$Invocation.InvocationName.LastIndexOf("\"));
    }
}

我喜欢单行解决方案:)

$scriptDir = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent

可靠的方法就像您显示的$ myinvoke . mycommand . path一样。

使用相对路径将基于PowerShell中的$pwd，应用程序的当前目录或. net API的当前工作目录。

PowerShell v3 +:

使用自动变量$PSScriptRoot。

要只获取当前文件夹名称，您还可以使用:

(Split-Path -Path (Get-Location) -Leaf)