New Features in Windows PowerShell 2.0

Remoting, script debugging, and other features fill PowerShell gaps

Executive Summary:
The release of Windows PowerShell 2.0 will add important new features to the PowerShell language and development experience, including new cmdlets, variables, and operators. The ability to run background jobs and for administrators to create ScriptCmdlets makes PowerShell 2.0 more versatile. Script degugging capabilities are enhanced both through cmdlet-based debugging and the Integrated Scripting Environment.

If you've wanted to take advantage of PowerShell scripting but found the learning curve a bit too steep, PowerShell 2.0 might be just the ticket you've been waiting for. Expected to be released in the second half of 2009, PowerShell 2.0 adds several important new features to the PowerShell language and development experience that make it easier to use as well as filling in some of the gaps that were present in PowerShell 1.0. My top ten favorite new features in PowerShell 2.0 follow.

10. New cmdlets—PowerShell 2.0 includes 24 new cmdlets. Some of the cmdlets work with debugging, Windows Management Instrumentation (WMI), and background jobs. Out-GridView is one of my favorites; this cmdlet displays the results of other commands in an interactive table so that you can sort and search the data displayed.

9. New operators—PowerShell 2.0 provides three useful new operators: @ (pronounced splat), -split, and -join. The @ operator passes a collection of parameters; -split breaks a string into an array; and -join concatenates multiple strings, adding separators.

8. New built-in variables—PowerShell 2.0 includes four new built-in variables: $commandLineParameters, $PSVersionTable, $Culture, and $UICulture. The $commandLineParameters variable accesses command line parameters. $PSVersionTable reports the current PowerShell version. $Culture and $UICulture report the current culture (i.e., the language setting on the target system) and UI culture information.

7. Try-Catch-Finally exception handling—Following in the footsteps of the other .NET languages, PowerShell 2.0 adds the standard Try-Catch-Finally structure to the PowerShell language. You use the Try block to safely execute one or more statements. If an error occurs, the code in the Catch block will be executed. An optional Finally block contains code that is run after the Try-Catch portion completes.

6. PowerShell Hosting APIs—Microsoft has included PowerShell scripting support in all its recent server products, including Exchange Server 2007, SQL Server 2008, and Windows Server 2008, as part of its Common Engineering Criteria. The new PowerShell Hosting APIs promise to extend PowerShell functionality to other products because it simplifies hosting PowerShell in applications.

5. Script debugging—Another important improvement in PowerShell 2.0 is its enhanced debugging capabilities. PowerShell 2.0 has a cmdlet-based debugger that lets you set breakpoints and step through your scripts using the PowerShell console window without needing any graphical development tools. To find out more about PowerShell 2.0's script debugging, run the command

get-help about_debugger 

4. Background jobs—One of the biggest gaps in PowerShell 1.0 is the inability to run a background process. This made it tough to replace those Windows Shell scripts that made use of the Start command. PowerShell 2.0's new Start-PSJob cmdlet asynchronously runs background jobs on the local system or on remote systems. For more information, you can run

get-help about_psjob 

3. ScriptCmdlets—In PowerShell 1.0, you need to program in .NET to create new cmdlets. This requirement means that typically only developers can make new cmdlets. Powershell 2.0 lets administrators create ScriptCmdlets using PowerShell itself. For more information about creating ScriptCmdlets, run

get-help about_scriptcmdletparameters
get-help about_scriptcmdletmethods

2. Remoting—One of the most important changes in PowerShell 2.0 is support for running scripts on remote systems. PowerShell Remoting lets you run scripts on remote networked systems. This new remoting support requires that PowerShell 2.0 be installed on both the local and remote systems. For more information, run

get-help about_remoting 

1. Integrated Scripting Environment—My favorite PowerShell 2.0 feature is the new Integrated Scripting Environment. ISE is a multitabbed graphical PowerShell development platform that features color-coded syntax. It also includes debugging capabilities that let you set breakpoints and step through your PowerShell scripts. If you've had trouble getting started with PowerShell, ISE will definitely kick start your PowerShell scripting.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.