There comes a time when you are neck deep in code, and come to the realization that one of your modules could really use a tweak.\u00a0 There is just one problem – what other scripts are using this module?\u00a0 What if you wanted to inventory your scripts and the modules that each script is using?\u00a0 This was the main use-case for this post.\u00a0 I have a scripts directory, and want to get a quick inventory of what modules each one is using.\u00a0\u00a0<\/p>\n
First, the function:<\/p>\n
#requires -version 3.0\nFunction Test-ScriptFile {\n <#\n .Synopsis\n Test a PowerShell script for cmdlets\n .Description\n This command will analyze a PowerShell script file and display a list of detected commands such as PowerShell cmdlets and functions. Commands will be compared to what is installed locally. It is recommended you run this on a Windows 8.1 client with the latest version of RSAT installed. Unknown commands could also be internally defined functions. If in doubt view the contents of the script file in the PowerShell ISE or a script editor.\n You can test any .ps1, .psm1 or .txt file.\n .Parameter Path\n The path to the PowerShell script file. You can test any .ps1, .psm1 or .txt file.\n .Example\n PS C:\\> test-scriptfile C:\\scripts\\Remove-MyVM2.ps1\n \n CommandType Name ModuleName\n ----------- ---- ----------\n Cmdlet Disable-VMEventing Hyper-V\n Cmdlet ForEach-Object Microsoft.PowerShell.Core\n Cmdlet Get-VHD Hyper-V\n Cmdlet Get-VMSnapshot Hyper-V\n Cmdlet Invoke-Command Microsoft.PowerShell.Core\n Cmdlet New-PSSession Microsoft.PowerShell.Core\n Cmdlet Out-Null Microsoft.PowerShell.Core\n Cmdlet Out-String Microsoft.PowerShell.Utility\n Cmdlet Remove-Item Microsoft.PowerShell.Management\n Cmdlet Remove-PSSession Microsoft.PowerShell.Core\n Cmdlet Remove-VM Hyper-V\n Cmdlet Remove-VMSnapshot Hyper-V\n Cmdlet Write-Debug Microsoft.PowerShell.Utility\n Cmdlet Write-Verbose Microsoft.PowerShell.Utility\n Cmdlet Write-Warning Microsoft.PowerShell.Utility\n\n .Notes\n Original script provided by Jeff Hicks at (https:\/\/www.petri.com\/powershell-problem-solver-find-script-commands)\n\n #>\n \n [cmdletbinding()]\n Param(\n [Parameter(Position = 0, Mandatory = $True, HelpMessage = \"Enter the path to a PowerShell script file,\",\n ValueFromPipeline = $True, ValueFromPipelineByPropertyName = $True)]\n [ValidatePattern( \"\\.(ps1|psm1|txt)$\")]\n [ValidateScript( { Test-Path $_ })]\n [string]$Path\n )\n \n Begin {\n Write-Verbose \"Starting $($MyInvocation.Mycommand)\" \n Write-Verbose \"Defining AST variables\"\n New-Variable astTokens -force\n New-Variable astErr -force\n }\n \n Process {\n Write-Verbose \"Parsing $path\"\n $AST = [System.Management.Automation.Language.Parser]::ParseFile($Path, [ref]$astTokens, [ref]$astErr)\n\n #group tokens and turn into a hashtable\n $h = $astTokens | Group-Object tokenflags -AsHashTable -AsString\n \n $commandData = $h.CommandName | where-object { $_.text -notmatch \"-TargetResource$\" } | \n ForEach-Object {\n Write-Verbose \"Processing $($_.text)\" \n Try {\n $cmd = $_.Text\n $resolved = $cmd | get-command -ErrorAction Stop\n if ($resolved.CommandType -eq 'Alias') {\n Write-Verbose \"Resolving an alias\"\n #manually handle \"?\" because Get-Command and Get-Alias won't.\n Write-Verbose \"Detected the Where-Object alias '?'\"\n if ($cmd -eq '?') { \n Get-Command Where-Object\n }\n else {\n $resolved.ResolvedCommandName | Get-Command\n }\n }\n else {\n $resolved\n }\n } \n Catch {\n Write-Verbose \"Command is not recognized\"\n #create a custom object for unknown commands\n [PSCustomobject]@{\n CommandType = \"Unknown\"\n Name = $cmd\n ModuleName = \"Unknown\"\n }\n }\n } \n\n write-output $CommandData\n }\n\n End {\n Write-Verbose -Message \"Ending $($MyInvocation.Mycommand)\"\n }\n}\n<\/pre>\n\u00a0<\/p>\n