$MyInvocation.MyCommand.Path is $null in PowerGUI script editor

Question

When trying to debug my powershell script in the powerGUI script editor (2.0.0.1082) the $MyInvocation.MyCommand.Path is $null. It works when running the script via powershell. Running it in Powershell_ise.exe (on one of our servers) also works fine.

Have anyone else had the same problem or know what's wrong?

Here's my powershell version:

Name                           Value
----                           -----
CLRVersion                     2.0.50727.4927
BuildVersion                   6.1.7600.16385
PSVersion                      2.0
WSManStackVersion              2.0
PSCompatibleVersions           {1.0, 2.0}
SerializationVersion           1.1.0.1
PSRemotingProtocolVersion      2.1

Server version:

Name                           Value
----                           -----
CLRVersion                     2.0.50727.3082
BuildVersion                   6.0.6002.18111
PSVersion                      2.0
WSManStackVersion              2.0
PSCompatibleVersions           {1.0, 2.0}
SerializationVersion           1.1.0.1
PSRemotingProtocolVersion      2.1

FYI: I read somewhere that it would be null when calling it from a function. I haven't done that. — Polymorphix, Jun 07 '10 at 11:38

George Howarth · Answer 1 · 2010-06-08T12:12:34.343

The $MyInvocation.MyCommand object changes depending on the context of its execution. In this case, $MyInvocation.MyCommand.Path will only return something if called from the $script: scope, since that is the only valid scope to determine the directory from which the code was executed.

Therefore, the solution here would either be to use $script:MyInvocation.MyCommand.Path or $MyInvocation.ScriptName.

EDIT

Running this in the PowerShell ISE works as expected, as you get the same result if you run it in the PowerShell console:

function Main
{
    Write-Host ("MyCommand.Path from function: " + $MyInvocation.MyCommand.Path)
    Write-Host ("ScriptName from function: " + $MyInvocation.ScriptName)
}

Main

Write-Host ("MyCommand.Path from script scope: " + $MyInvocation.MyCommand.Path)
Write-Host ("ScriptName from script scope: " + $MyInvocation.ScriptName)

Output is:

MyCommand.Path from function: 
ScriptName from function: C:\temp\Test.ps1
MyCommand.Path from script scope: C:\temp\Test.ps1
ScriptName from script scope:

I haven't used PowerGUI, but if you don't get the same output, then its probably a bug.

None of them gives me anything but $null. And as $MyInvocation.MyCommand.Path is called in the first line in the script outside any function, my limited powershell knowledge tells me it's already in the $script scope. I think it's actually a bug in ScriptEditor, as it works fine when run from the prompt. — Polymorphix, Jun 08 '10 at 07:48

score 1 · Answer 2 · answered Jun 15 '10 at 09:59

1

call your script from another script file: http://powergui.org/message.jspa?messageID=28988#28988

answered Jun 15 '10 at 09:59

ulku

41
3

score 1 · Accepted Answer · answered Jan 20 '11 at 18:52

1

This issue has been fixed. Download the latest version of PowerGUI from http://powergui.org and the issue will disappear.

answered Jan 20 '11 at 18:52

DSotnikov

634
3
10

Thanks for following this up. :) – Polymorphix Feb 14 '11 at 09:06
3

I'm running the latest version (3.5.0.2293) and still seem to have this issue. – Alex Feb 21 '13 at 10:59

score 0 · Answer 4 · answered Jun 07 '10 at 17:23

0

You might want to try using Get-PSCallStack. The InvocationInfo property of each layer in the callstack is the equivilent to $myInvocation

Hope this helps.

answered Jun 07 '10 at 17:23

Start-Automating

8,067
2
28
47

Thank you, that sounds like a useful tool. When running the script from the ScriptEditor debugger, the Command from Get-PSCallStack is '.', but when running the script from the prompt it is the name of my script. – Polymorphix Jun 08 '10 at 08:08

$MyInvocation.MyCommand.Path is $null in PowerGUI script editor

4 Answers4

Linked