As you might imagine I write a lot of PowerShell scripts and examples. Often my PowerShell Window is open for days at a time. One challenge I have always has is trying to remember what variables I have defined. If I knew the name I'd simply use Get-Variable. What I really want is a way to see just the variables that I've created. So I wrote a function to do just that. As an added benefit I can also export these variables and re-import them into another PowerShell session.<\/p>\n
Here's the function's core code, less the comment based help.<\/p>\n
[cc lang=\"PowerShell\"]
\nFunction Get-MyVariable {<\/p>\n
[cmdletbinding()]<\/p>\n
Param(
\n [Parameter(Position=0)]
\n [ValidateSet(\"Global\",\"Local\",\"Script\",\"Private\",0,1,2,3)]
\n [ValidateNotNullOrEmpty()]
\n [string]$Scope=\"Global\")<\/p>\n
if ($psise)
\n {
\n Write-Warning \"This function is not designed for the PowerShell ISE.\"
\n }
\n else
\n {
\n Write-Verbose \"Getting system defined variables\"
\n #get all global variables from PowerShell with no profiles
\n $psvariables=powershell -noprofile -COMMAND \"& {GET-VARIABLE | select -expandproperty name}\"
\n Write-Verbose \"Found $($psvariables.count)\"<\/p>\n
#find all the variables where the name isn't in the variable we just created
\n #and also isn't a system variable generated after the shell has been running
\n #and also any from this function
\n Write-Verbose \"Getting current variables in $Scope scope\"
\n $variables=Get-Variable -Scope $Scope
\n Write-Verbose \"Found $($variables.count)\"
\n Write-Verbose \"Filtering variables\"
\n #define variables to also exclude
\n $skip=\"LastExitCode|_|PSScriptRoot|skip|PSCmdlet|psvariables|variables|Scope\"
\n $variables | Where {$psvariables -notcontains $_.name -AND $_.name -notmatch $skip}
\n Write-Verbose \"Finished getting my variables\"
\n }
\n} #end function
\n[\/cc]<\/p>\n
As I was developing this function, Get-MyVariable, I originally was focused on the global scope. But then I realized I could also use something like this to track variables defined in a script or function. Thus the function includes a parameter called -Scope with a default value of Global. You can use any of the parameters that you would use with any of the Variable cmdlets, ie Global, Local, Script or Private. You can also use an integer to indicate the scope level. A value of 0 means the current scope. A value of 1 is the parent scope, 2 is the next scope up and so on. I limited my function to 5 which should be more than enough. What this means is that I can run a command like this and check the state of all my variables.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS C:\\> function foo { . s:\\get-myvariable.ps1;$a=4;$b=2;$c=$a*$b;get-MyVariable -scope 1 -verbose;$c}
\n[\/cc]<\/p>\n
The Get-MyVariable function has it's own scope so by specifying a scope of 1 I get the variables defined in the foo function.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS S:\\> foo
\nVERBOSE: Getting system defined variables
\nVERBOSE: Found 49
\nVERBOSE: Getting current variables in 1 scope
\nVERBOSE: Found 27
\nVERBOSE: Filtering variables<\/p>\n
Name Value
\n---- -----
\na 4
\nb 2
\nc 8
\nVERBOSE: Finished getting my variables
\n8
\n[\/cc]<\/p>\n
The function works by launching a separate PowerShell console session without any profiles to capture all variables. This should be all the variables defined by PowerShell. All I want is an array of the variable names.<\/p>\n
[cc lang=\"PowerShell\"]
\n$psvariables=powershell -noprofile -COMMAND \"& {GET-VARIABLE | select -expandproperty name}\"
\n[\/cc]<\/p>\n
Then all I have to do is get variables from the specified scope and filter out those that aren't from PowerShell as well as those defined in the Get-MyVariable function.<\/p>\n
[cc lang=\"PowerShell\"]
\n$variables=Get-Variable -Scope $Scope
\n#define variables to also exclude
\n$skip=\"LastExitCode|_|PSScriptRoot|skip|PSCmdlet|psvariables|variables|Scope\"
\n$variables | Where {$psvariables -notcontains $_.name -AND $_.name -notmatch $skip}
\n[\/cc]<\/p>\n
The script containing this function also defines an alias, gmv<\/I>. You can comment out if you don't want to use it. I've added this function to my profile. Now, if I need to \"move\" variables between sessions or even computers, I can export them to an XML file.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS C:\\> Get-MyVariable | Export-Clixml myvar.xml
\n[\/cc]<\/p>\n
You can then import this xml file in another session to restore these variables. This assumes you are only worried about global variables in your console session.<\/p>\n
[cc lang=\"PowerShell\"]
\nPS C:\\> import-clixml f:\\files\\myvar.xml | foreach {set-variable -Name $_.name -Value $_.value}
\n[\/cc]<\/p>\n
One caveat: depending on your variables your XML file could get quite large. During testing I had a variable defined like this.<\/p>\n
[cc lang=\"PowerShell\"]
\n$evt=Get-Eventlog -list
\n[\/cc]<\/p>\n
My XML file was over 17MB in size. <\/p>\n
One final note is that this function is designed to work with the PowerShell console, not the ISE. In fact, I have code to check if you are running it in the ISE. The varaiable, $psise, refers to the ISE object.<\/p>\n
[cc lang=\"PowerShell\"]
\nif ($psise)
\n{
\n Write-Warning \"This function is not designed for the PowerShell ISE.\"
\n }
\n[\/cc]<\/p>\n
The ISE introduces it's own set of default variables. But since I primarily use the console, I didn't bother finding an easy way to filter them out. Feel free to work out that for yourself.<\/p>\n