Constant and Read-Only PowerShell Variables for Admins Who Fear Change
bucket that stuff goes into, comes out of, gets changed and gets removed. However, there’s a certain subset of PowerShell variables that can be defined but can never change. These sets are called constants and read-only variables.
Constants and read-only variables are pretty much functionally equivalent. Values are assigned to a constant or read-only variable, but can never change. In the case of an actual constant, it can’t even be removed. Let’s go over a quick example.
If you’ve written scripts in PowerShell you’ve most likely assigned variables in the form $Variable = 'some value' . This is common practice and is the typical way in which a variable is defined. But there is a built-in PowerShell cmdlet called Set-Variable that can assign variable values as well. It’s not as commonly used because writing $Bucket = 'Full' and Set-Variable -Name 'Bucket' -Value 'Full' are functionally equivalent.
I created that $Bucket variable and assigned it a value of Full. I then changed the value of $Bucket to Empty. But what if I want to create a constant? In that case, use Set-Variable with an additional parameter called Option . By using the Option parameter, admins can assign the $Bucket variable as always being ‘Full… Continue reading on SearchWindowsServer.
Latest posts by Adam Bertram (see all)
- Review: Ansible shows the beef - January 19, 2017
- PowerShell integration tests with Pester - January 19, 2017
- Update multiple SQL Server systems with PowerShell - January 18, 2017