I have several PowerShell scripts that use directory dependencies to process other files, and for this I use the $PSScriptRoot automatic variable. However, when I try to run these scripts from a VisualCron PowerShell task, the value of $PSScriptRoot is null and I tend to have to hard-code a path. Why is this variable not populated? Are any automatic variables populated in the VC PowerShell host? Thanks!

Since we are using the PowerShell this Variables is not available. You can try;

$ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath(‘.\’)

https://msdn.microsoft.c...mp;MSPPError=-2147217396 

---

Not sure I understand the above - what prevents this from being available? Are any of the automatic variables available?

Unfortunately, the command above will return the current working directory instead of the path of the currently executing script, and these are not the same thing.

Not sure I understand the above - what prevents this from being available? Are any of the automatic variables available?

Unfortunately, the command above will return the current working directory instead of the path of the currently executing script, and these are not the same thing.

I cannot answer if there is an exact equvivalent of your command but the reason some commands does not work is that the PowerShell host is a different engine than PowerShell.exe. It does not have a process by its own - it is hosted in other applications. Because of that, commands and features are slightly different. You always have the option to call PowerShell.exe if you cannot get something to work.

---

Not sure I understand the above - what prevents this from being available? Are any of the automatic variables available?

Unfortunately, the command above will return the current working directory instead of the path of the currently executing script, and these are not the same thing.

I cannot answer if there is an exact equvivalent of your command but the reason some commands does not work is that the PowerShell host is a different engine than PowerShell.exe. It does not have a process by its own - it is hosted in other applications. Because of that, commands and features are slightly different. You always have the option to call PowerShell.exe if you cannot get something to work.

That might be what I do in the short term to resolve this problem, and potentially work toward transforming my project to be less dependent on the script's path. As a workaround, though, is it possible to set the working directory for PowerShell tasks the way that you can for CMD?

Thanks!

Not sure I understand the above - what prevents this from being available? Are any of the automatic variables available?

Unfortunately, the command above will return the current working directory instead of the path of the currently executing script, and these are not the same thing.

I cannot answer if there is an exact equvivalent of your command but the reason some commands does not work is that the PowerShell host is a different engine than PowerShell.exe. It does not have a process by its own - it is hosted in other applications. Because of that, commands and features are slightly different. You always have the option to call PowerShell.exe if you cannot get something to work.

That might be what I do in the short term to resolve this problem, and potentially work toward transforming my project to be less dependent on the script's path. As a workaround, though, is it possible to set the working directory for PowerShell tasks the way that you can for CMD?

Thanks!

Not right now, please create a Feature request in the Feature requests forum.

---