IT:AD:Powershell:HowTo:gotchas/Different behaviour between ide and runtime

• (UP)

  • configure
    • IT:AD:Powershell:HowTo:Configure:For Git
  • IT:AD:PowerShell:HowTo:ByPass the PowerShell Execution Policy
  • IT:AD:PowerShell:HowTo:Create A Self-Signed Certificate
  • it:ad:powershell:Howto:Debug using VS Code
  • it:ad:powershell:howto:Force An Array Result
  • IT:AD:PowerShell:HowTo:Gotchas
  • it:ad:powershell:howto:recursively_rename_files:Home
  • IT:AD:Powershell:HowTo:Run scripts within the Package Manager Console
    • IT:AD:Powershell:HowTo:Run scripts within the Package Manager Console/Background Info
  • IT:AD:PowerShell:HowTo:Snippets
    • IT:AD:PowerShell:HowTo:Snippets:Multi-Threading
    • IT:AD:powershell/howto/snippets/working with modules
    • IT:AD:powershell/howto/snippets/work with bools
    • IT:AD:Powershell/Howto/Snippets/work with directories
    • IT:AD:Powershell/Howto/Snippets/Work with files
    • IT:AD:PowerShell:HowTo:Snippets:Check Powershell Version
    • IT:AD:Powershell:HowTo:Snippets:Configure SSH
    • IT:AD:Powershell:HowTo:Snippets:Ensure a Local User Account
    • IT:AD:Powershell:HowTo:Snippets:How Should I Trace.Write
    • IT:AD:Powershell:HowTo:Snippets:Install Chocolatey
    • IT:AD:PowerShell:HowTo:Snippets:Refresh Environment Variables
    • IT:AD:PowerShell:HowTo:Snippets:Update Execution Policy
    • IT:AD:Powershell:HowTo:Snippets:Upload and download files
    • IT:AD:Powershell:HowTo:Snippets:Use Chocolatey to install tools
    • IT:AD:Powershell:HowTo:Snippets:Wait for User Input
    • IT:AD:Powershell:HowTo:Snippets:Working with certificates
    • IT:AD:Powershell:HowTo:Snippets:Working with Scripts
    • IT:AD:Powershell:HowTo:Snippets:Work with Environment Variables
    • IT:AD:Powershell:HowTo:Snippets:Work with FileNames
    • IT:AD:PowerShell:HowTo:Snippets:work with strings
    • IT:AD:Powershell:HowTo:Snippets:Work with Variables
  • IT:AD:Powershell:HowTo:Syntax Basics
  • IT:AD:Powershell:HowTo:Work with Environment Variables
  • IT:AD:Powershell:HowTo/Accessing Static .NET Methods and Properties
  • IT:AD:Powershell:HowTo/Run a PS Script File from a Command line
  • IT:AD:Powershell:HowTo/Run a script, redirecting all output to a file
  • IT:AD:Powershell:HowTo/Write Output containing Sub Properties
  • IT:AD:Powershell:HowTo:Add a WhatIf Switch To Test Dangerous Logic
  • IT:AD:Powershell:HowTo:Automate Visual Studio
  • IT:AD:Powershell:HowTo:Choose the Right Verb For Module Method Names
  • IT:AD:Powershell:HowTo:Configure ExecutionPolicy
  • IT:AD:Powershell:HowTo:Control Output
  • IT:AD:PowerShell:HowTo:Create a Function
  • IT:AD:Powershell:HowTo:Create a Powershell Module
  • IT:AD:PowerShell:HowTo:Create Variables
  • IT:AD:Powershell:HowTo:Examples
  • IT:AD:powershell:HowTo:Execute A Dll From The Command Line
  • IT:AD:Powershell:HowTo:Get Git and SSH to work
  • IT:AD:Powershell:HowTo:gotchas/Different behaviour between ide and runtime
  • IT:AD:PowerShell:HowTo:Gotchas/Function Returns
  • IT:AD:Powershell:HowTo:Install
  • IT:AD:Powershell:HowTo:Invoke a File
  • IT:AD:Powershell:HowTo:Query a Database
  • IT:AD:Powershell:HowTo:Script/Admin Operations/Users
  • IT:AD:Powershell:HowTo:Unit Test
  • IT:AD:Powershell:HowTo:Use .NET4+ Assemblies
  • IT:AD:Powershell:HowTo:Use an App.Config
  • it:adpowershell howto gotchas modules scripts and dot sourcing

A lot of scripts rely on loading other scripts and files from the the same or descendent directories.

That means that the script has to figure out where it is first, in order to it's directory.

You would think that's easy… I wish it were.

You'll see lots of scripts state something akin to:

	$currentDirectory = (Split-Path $MyInvocation.MyCommand.Path)[0];

But it only works when run not in the IDE!

And the workaround for Powershell v1 is not:

	$currentDirectory = $MyInvocation.MyCommand.Path;
	if (!$currentDirectory.Path){
                # this is garbage...it totally depends where you opened the CLI from...
		$currentDirectory = (Get-Location).Path
	}
	else {
		$currentDirectory = (Split-Path $tmp)[0];
	}

But in V3, the following do work in the IDE and runtime:

• $PSCommandPath
• $PSScriptRoot
  • WARNING: saw this, but I disagree as it's working for me right now in Powershell 4:

    • https://connect.microsoft.com/PowerShell/feedback/details/522951/psscriptroot-only-works-with-modules

    Which is more or less the equivalent of (it it would have worked in the IDE as well):

$private:PSCommandPath = $MyInvocation.MyCommand.Path
$private:PSScriptRoot = (Split-Path -Parent $PSCommandPath)