The Windows PowerShell Team is pleased to release the second Community Technology Preview (CTP2) of Windows PowerShell V2!
This release adds a plethora of new features. PowerShell remoting now allows a one-to-one interactive experience. Thought about partitioning and organizing PowerShell scripts? Use modules to create self-contained and reusable units. This release introduces transactions support in PowerShell engine and APIs along with an update to the Registry provider to support them. We introduced eventing support in Powershell engine for listening, forwarding and acting on management and system events. Support for multiple parameter sets in script cmdlets bring them to par with C# cmdlets. For the adventurous folks…. application developers can host PowerShell in IIS to support multiple remote PowerShell sessions in a single process. These are just a few of the new features we have packaged in this CTP2 release. Additionally this CTP2 includes some simple updates… like new parameters to several existing cmdlets. More feature descriptions and details are in the Release Notes and in the “about” topics included with the installation.
Reminder to the brave souls who want to use these bits in a production environment … Don’t.
This CTP is not a beta. This software is a pre-release version. It will not work the way a final version of the software does. These CTP2 bits have not gone through rigorous testing. Even with these caveats, we hope you would try them out and let us know your feedback.
Last but certainly not least, V2 builds upon Windows PowerShell 1.0 by providing backward compatibility – your 1.0 cmdlets and scripts will run on this CTP2 (with the exceptions noted in the Release Notes – mostly new keywords/cmdlets). If a working 1.0 script doesn’t run on V2 and is not in the known list of exceptions, please tell us about it!
Download WinRM 2.0 CTP (required for PowerShell remoting)
Hemant Mahawar [MSFT]
Program Manager
Windows PowerShell
Submitting Feedback
Please submit your feedback using the Connect Website (adding a CTP2: to the title), posting on the Windows PowerShell Discussion Group, or commenting on the Windows PowerShell Blog
0 comments