SAPIEN Solutions

Use 'single quotation marks' around string literals unless you explicitly need variable expansion. In PowerShell, single quotes are not expanded into variables: $var = 'Hello' $result = '$var $var' # $result contains '$var $var' Double quotes are: $var = 'Hello' $result = "$var $var" # $result contains 'Hello Hello' To…   More »

Whenever possible, functions (especially) and scripts (to a lesser degree) should emit custom objects, not just text. This ensures that the output of these constructs can be piped to other cmdlets, like Where-Object, Sort-Object, and so forth, further extending PowerShell's capabilities. To create a custom object: $obj = New-Object PSObject…   More »

Develop a standard for formatting your scripts, and use indentation. Function MyFunction { # function code here } ...or... Function MyFunction { # function code here }…   More »

Aliases are harder to read and maintain over the long term - so try and avoid using them in a script. If you use PrimalScript, just select Edit > Convert > Alias to Cmdlet to turn all aliases into their full cmdlet names, providing easier long-term maintenance and readability for…   More »

Scripts, functions, and other elements should NEVER modify the variables, aliases, PSDrives, or other items from parent scopes. Instead, return data to the parent scope using the pipeline. Changing parent scope items creates code which is much more difficult to debug and maintain, and can create inconsistent results when run…   More »