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 Feb 8, 2017
Created on Feb 8, 2017

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.

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 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.

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
54% 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 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
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
51% 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
50% match
Loading thumbnail…

Gist 22232677b43d0904992cd489d2aafdf0

This example demonstrates a shell script that automates the setup of a Linux scavenger hunt lab environment. It creates a directory, clones a Git repository from GitLab, initializes submodules, and uses Vagrant to launch a virtual machine. The script then runs a PowerShell reprovisioner script and fixes line endings with `dos2unix` before executing the reprovisioning process. The visualization—if any—is not present; the code focuses purely on environment provisioning using Git, Vagrant, and PowerShell APIs.

PPeleke
50% match
Loading thumbnail…

Gist 6378827722c371d2f33b9a9516ab1017

This example shows a PowerShell automation script for provisioning a cybersecurity lab environment. It uses the Vagrant command-line interface to add a Hyper-V provider machine image and start a virtual machine from a copied Vagrantfile. The script relies on PowerShell cmdlets like `mkdir` and `cp` alongside Vagrant’s `box add` and `up` commands to set up the Linux scavenger environment from a preconfigured gist.

PPeleke
49% match