PowerShell Windows

PowerShell Best Practices: Set-StrictMode

During some research for PowerShell best practices I came across the following blog post on the Hey Scripting Guy Blog from Microsoft:
http://blogs.technet.com/b/heyscriptingguy/archive/2014/12/03/enforce-better-script-practices-by-using-set-strictmode.aspx

By using the Set-StrictMode cmdlet, we can enforce some common “best practice” coding techniques that you can use with your scripts. In yesterday’s post, I used the –Strict parameter with Set-PSDebug. This enforces the variable declaration in a script. But with Set-StrictMode, we get that plus a little more. The scope is limited to the current scope and child scopes. By default, Set-StrictMode is turned off to prevent error messages while you are writing the script.

From now on, all my PowerShell scripts will start with “Set-StrictMode -Version latest” and “Set-PSDebug -Strict”:

Set-PSDebug -Strict
Set-StrictMode -Version latest
You may also like
Update environment variables in current process
Change DNS settings on multiple Windows Servers and Workstations
Assign Office 365 licenses based on Active Directory groups

Leave Your Comment

Your Comment*

Your Name*
Your Webpage