How to get the current file location in PowerShell

Question

I am wondering how to get the location of the script I am running or writing. We have a set of .NET assemblies placed in the same directory as the current PowerShell script, and we want load them from the script. Right now I am using a fixed path to locate assemblies, but we want to load them from the current file location.

[System.Reflection.Assembly]::LoadFrom
("C:\Work\Scripts\Assemblies\DynamicOps.ManagementModel.Client.dll")

[System.Reflection.Assembly]::LoadFrom
("C:\Work\Scripts\Assemblies\DynamicOps.Repository.dll")

Same question here: stackoverflow.com/questions/9063964/…

CB.
– CB.

2012-05-18 12:24:22 +00:00
Commented May 18, 2012 at 12:24 — CB.
– CB., Commented May 18, 2012 at 12:24

JPBlanc · Accepted Answer · 2012-05-18 13:56:32Z

12

$MyInvocation

Contains an object with information about the current command, such as a script, function, or script block. You can use the information in the object, such as the path and file name of the script ($myinvocation.mycommand.path) or the name of a function ($myinvocation.mycommand.name) to identify the current command. This is particularly useful for finding the name of the script that is running. You'll get full help on automatic varible with about_Automatic_Variables :

get-help about_Automatic_Variables -full

(Edited) To get current directory you've got the CmdLet Get-Location

edited May 18, 2012 at 13:56

answered May 18, 2012 at 12:24

JPBlanc

73.1k17 gold badges137 silver badges180 bronze badges

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

3 Comments

user1358784 Over a year ago

thanks JPBlanc! I tried with split-Path and it worked. $currentFileLocation = Split-Path $MyInvocation.MyCommand.Path

user1358784 Over a year ago

I moved $currentFileLocation = Split-Path $MyInvocation.MyCommand.Path line of code to function and it does not work. It throws an error while running a script , any suggestions? PS C:\Windows\system32> C:\Work\Scripts\GetVirtualMachineProvisiongGroup.ps1 Write-Error : Cannot bind argument to parameter 'Path' because it is null.

JasonMArcher Over a year ago

$MyInvocation is an automatic variable. If you write a function to do this, you need to grab the $MyInvocation from the parent scope. Read this article (blogs.msdn.com/b/powershell/archive/2007/06/19/…).

David Brabant · Accepted Answer · 2012-05-18 12:24:26Z

2

$MyInvocation.MyCommand.Path maybe?

answered May 18, 2012 at 12:24

David Brabant

44k16 gold badges93 silver badges119 bronze badges

Collectives™ on Stack Overflow

How to get the current file location in PowerShell

2 Answers 2

3 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related