Skip to main content
100%

Use different techniques to determine a PowerShell script's directory: try `$PSScriptRoot`, `$MyInvocation.MyCommand.Path`, `$ExecutionContext.SessionState.Module.Path` and `$PWD`.

✓ Published0🌍 Public
Aaniston
Last edited May 2, 2014
Created on Feb 8, 2017

This example demonstrates a PowerShell script that determines its own directory using four distinct fallback techniques. It checks the `$PSScriptRoot` automatic variable first, then falls back to `$MyInvocation.MyCommand.Path`, followed by `$ExecutionContext.SessionState.Module.Path`, and finally defaults to `$PWD`. The code uses PowerShell’s built-in `Get-Variable` cmdlet and `Split-Path` function to extract and normalize the directory path from each source. It shows how to handle various execution contexts, such as scripts run directly, invoked from modules, or executed interactively, prioritizing the most reliable method first.

AI-generated description

Similar vizzes

Loading thumbnail…

Use different techniques to determine a PowerShell script's directory: try `$PSScriptRoot`, `$MyInvocation.MyCommand.Path`, `$ExecutionContext.SessionState.Module.Path` and `$PWD`.

This example demonstrates a PowerShell script that attempts to locate its own directory using four different techniques in a fallback sequence: `$PSScriptRoot`, `$MyInvocation.MyCommand.Path`, `$ExecutionContext.SessionState.Module.Path`, and finally `$PWD`. The code defines a function `Get-ScriptPath` that checks each variable in order, using `Split-Path` to extract the parent directory when necessary. It shows the logic for handling environments where certain automatic variables may be unavailable, such as when the script is invoked from a module or interactive session. The example relies on PowerShell’s built-in `Get-Variable` cmdlet and conditional checks to progressively resolve the path.

Aaniston
94% match
Loading thumbnail…

powershell wtf

This example illustrates a PowerShell script that extracts a changeset ID from a Git commit message using two different approaches. It first demonstrates a successful method using a `Where-Object` pipeline with a regular expression, followed by a direct `-Match` operator, both printing the captured group to the console. The script then shows a commented-out version where the `-Match` operator fails, producing a "Cannot index into a null array" error, highlighting the difference in handling matched results. The code relies on PowerShell's built-in regex matching and `Write-Host`, drawing data from `git log`.

RRestuta
55% match
Loading thumbnail…

Gist 64e48e594d78f24f4f91dda25974c90c

This example shows a PowerShell script for automating the setup of a Windows development environment, with a focus on configuring Hyper-V and WSL. The script uses Chocolatey commands to install tools like Docker Desktop, Git, Node.js, and Visual Studio Code, while also enabling Windows features and disabling UAC. It downloads GitLab Runner and registers it as a service, then fetches Ubuntu 18.04 Appx and Vagrant files for later WSL and Hyper-V use. The code relies on the Chocolatey package manager and Windows PowerShell cmdlets.

PPeleke
53% match
Loading thumbnail…

My PowerShell profile. To edit yours type `code $profile`

This example visualizes a developer’s PowerShell profile, showing how aliases and functions streamline common workflows. It renders the profile’s source code as text, highlighting the use of posh-git for prompt customization and the `Set-Alias` and `function` keywords to map commands like `yarn build` to `b`. The code also references `$GitPromptSettings` to adjust the prompt’s prefix and suffix, and sets environment variables like `$HOME`. The visualization is a static code snippet, with no external libraries or data sources beyond the profile’s own content.

HHerbCaudill
53% match
Loading thumbnail…

Adds GitExtensions support to the git bash

This example demonstrates a PowerShell script that configures the Git Bash environment to integrate with GitExtensions. The script first detects the operating system architecture using `Get-WMIObject` to determine the appropriate Git installation path, then modifies the system `PATH` variable by appending the Git directory. It subsequently creates a `git-ex` file in the Git `bin` folder, writing a shell script content that launches `GitExtensions.exe` with any passed arguments. The code uses PowerShell's `Write-Host` for user feedback and `Test-Path` and `New-Item` for file operations.

RRestuta
52% match
Loading thumbnail…

Gist bae6758b4e3645b55f022e6432f29458

This visualization demonstrates the interaction between R and PowerShell, showing how a system call from an R environment triggers a PowerShell script that manipulates data. The code uses the `system2` function to execute a PowerShell command with a specified file path, passing arguments to run `coolScript.ps1`. The example highlights the practical integration of two scripting environments, where R serves as the orchestrator for external process execution. The rendering relies on the command-line interface rather than graphical libraries, focusing on the workflow of invoking and managing external scripts from within an R session. The data flow is implicit in the script's execution, emphasizing interoperability over visual output.

HHugoberry
52% match
Loading thumbnail…

Gist b588efbfbdbd8c9b4be6d634dbc61483

This example shows a PowerShell script for preparing a Windows machine for remote management and cloning. It configures WinRM by setting memory and timeout limits, enabling basic authentication, and allowing unencrypted traffic, and it disables UAC and NLA through registry edits via `New-ItemProperty`. The code also invokes `Dism` to install .NET Framework 3.5, uses `cleanmgr.exe` for disk cleanup, and downloads Sysinternals' SDelete via `Invoke-WebRequest` to zero free space.

PPeleke
51% match
Loading thumbnail…

Gist 759f990ca4ab64414550b681a9f66f0e

This example demonstrates how to automate the setup of a Linux virtual machine for a scavenger-hunt challenge using PowerShell and Vagrant. It shows the complete provisioning workflow, starting with adding a Hyper-V provider box, creating a destination directory, downloading a Vagrantfile from a GitHub gist via `Invoke-WebRequest`, and finally running `vagrant up` to launch the machine. The code relies on Vagrant’s Hyper-V provider, the `vagrant box add` command, and PowerShell’s file and web-request cmdlets. The data source is the remote Vagrantfile hosted on GitHub, fetched over HTTP.

PPeleke
51% match