Running $PSScriptRoot in Selected Code

by Jul 15, 2022

Categories

Tags

Administration agent-based monitoring Agentless Monitoring alert responses alert thresholds alerting Alerts Amazon Aurora Amazon EC2 Amazon RDS Amazon RDS / Aurora Amazon RDS for SQL Server Amazon Redshift Amazon S3 Amazon Web Services (AWS) Analytics application monitoring Aqua Data Studio automation availability Azure Azure SQL Database azure sql managed instance Azure VM backup Backup and recovery backup and restore backup compression backup status Backup Strategy backups big data Blocking bug fixes business architecture business data objects business intelligence business process modeling business process models capacity planning change management cloud cloud database cloud database monitoring cloud infrastructure cloud migration cloud providers Cloud Readiness Cloud Services cloud storage cloud virtual machine cloud VM clusters code completion collaboration compliance compliance audit compliance audits compliance manager compliance reporting conference configuration connect to database cpu Cross Platform custom counters Custom Views customer survey customer testimonials Dark Theme dashboards data analysis Data Analytics data architect data architecture data breaches Data Collector data governance data lakes data lineage data management data model data modeler data modeling data models data privacy data protection data security data security measures data sources data visualization data warehouse database database administration database administrator database automation database backup database backups database capacity database changes database community database connection database design database developer database developers database development database diversity Database Engine Tuning Advisor database fragmentation database GUI database IDE database indexes database inventory management database locks database management database migration database monitoring database navigation database optimization database performance Database Permissions database platforms database profiling database queries database recovery database replication database restore database schema database security database support database synchronization database tools database transactions database tuning database-as-a-service databases DB Change Manager DB Optimizer DB PowerStudio DB2 DBA DBaaS DBArtisan dBase DBMS DDL Debugging defragmentation Demo diagnostic manager diagnostics dimensional modeling disaster recovery Download drills embedded database Encryption End-user Experience entity-relationship model ER/Studio ER/Studio Data Architect ER/Studio Enterprise Team Edition events execution plans free tools galera cluster GDPR Getting Started Git GitHub Google Cloud Hadoop Healthcare high availability HIPAA Hive hybrid clouds Hyper-V IDERA IDERA ACE Index Analyzer index optimization infrastructure as a service (IaaS) infrastructure monitoring installation Integrated Development Environment interbase Inventory Manager IT infrastructure Java JD Edwards JSON licensing load test load testing logical data model macOS macros managed cloud database managed cloud databases MariaDB memory memorystorage memoryusage metadata metric baselines metric thresholds Microsoft Azure Microsoft Azure SQL Database Microsoft PowerShell Microsoft SQL Server Microsoft Windows MongoDB monitoring Monitoring Tools Monyog multiple platforms MySQL news newsletter NoSQL Notifications odbc optimization Oracle PeopleSoft performance Performance Dashboards performance metrics performance monitoring performance schema performance tuning personally identifiable information physical data model Platform platform as a service (PaaS) PostgreSQL Precise Precise for Databases Precise for Oracle Precise for SQL Server Precise Management Database (PMDB) product updates Project Migration public clouds Query Analyzer query builder query monitor query optimization query performance Query Store query tool query tuning query-level waits Rapid SQL rdbms real time monitoring Real User Monitoring recovery regulations relational databases Releases Reporting Reports repository Restore reverse engineering Roadmap sample SAP Scalability Security Policy Security Practices server monitoring Server performance server-level waits Service Level Agreement SkySQL slow query SNMP snowflake source control SQL SQL Admin Toolset SQL CM SQL code SQL coding SQL Compliance Manager SQL Defrag Manager sql development SQL Diagnostic Manager SQL Diagnostic Manager for MySQL SQL Diagnostic Manager for SQL Server SQL Diagnostic Manager Pro SQL DM SQL Doctor SQL Enterprise Job Manager SQl IM SQL Inventory Manager SQL Management Suite SQL Monitoring SQL Performance SQL Quality SQL query SQL Query Tuner SQL Safe Backup SQL script SQL Secure SQL Security Suite SQL Server sql server alert SQL Server Migration SQL Server Performance SQL Server Recommendations SQL Server Security SQL statement history SQL tuning SQL Virtual Database sqlmemory sqlserver SQLyog Storage Storage Performance structured data Subversion Support tempdb tempdb data temporal data Tips and Tricks troubleshooting universal data models universal mapping unstructured data Uptime Infrastructure Monitor user experience user permissions Virtual Machine (VM) web services webinar What-if analysis WindowsPowerShell

One of the big pitfalls in PowerShell code is the automatic variable $PSScriptRoot which always holds the path to the folder the current script is located. This however requires that (a) the current script is in fact already saved to file, and (b) you are executing the entire file, i.e., by pressing F5.

When you execute only a selection of code using F8, even if you select the entire code, $PSScriptRoot is empty, and your selected code will run into errors because of this.

In the PowerShell ISE, however, it is simple to add a workaround to enable running $PSScriptRoot in selected code. Here is the code that you need to run:


function Invoke-Selection
{ 
    try
    {
        # get the selected text:
        $selectedText = $psise.CurrentFile.Editor.SelectedText
        # if no text was selected...
        if ($selectedText.Length -eq 0) {
            # ...select the line the caret is in and get this line instead: 
            $psise.CurrentFile.Editor.SelectCaretLine() 
            $selectedText = $psise.CurrentFile.Editor.SelectedText
        }

        # try and parse the code
        $sb = [ScriptBlock]::Create($selectedText)
    
        # get the missing variable content from the underlying file:
        $currentFile = $psise.CurrentFile.FullPath
        $currentFolder = Split-Path -Path $currentFile
    
        # append the selected code with these automatic variables, and set them:
        $runcode = @"
        `$PSCommandPath = '$currentFile'
        `$PSScriptRoot = '$currentFolder'
        $selectedText
"@
        # turn text into script block...
        $scriptblock = [ScriptBlock]::Create($runcode)
        # ...and execute it without private scope:
        . $scriptblock
    
    }
    catch
    {
        throw $_.Exception
    }

}
$null = $psise.CurrentPowerShellTab.AddOnsMenu.Submenus.Add('ExecuteSelection', {. Invoke-Selection}, 'SHIFT+F8') 

The code adds a new command to ISE that can be invoked by pressing CTRL+F8. Now, when you select code, and you would like to run it even though it contains $PSScriptRoot, simply press CTRL+F8 instead of F8, and it will run.

The key shortcut invokes the function Invoke-Selection. This function will take the currently selected text, add the missing automatic variables $PSScriptRoot and $PSCommandPath to the code and define these based on the current file path of the current script. Then it invokes the script block.

This way you now can debug and demo any selected code, even if it contains automatic variables. Just make sure you saved your script somewhere so PowerShell knows which locations your code is referring to.

 


Twitter This Tip! ReTweet this Tip!