The Community Technology Preview (CTP) of Windows PowerShell 2.0

The Community Technology Preview (CTP) of Windows PowerShell 2.0

  • Comments 20

 

The Windows PowerShell Team is pleased to release the first Community Technology Preview (CTP) of Windows PowerShell 2.0!

This release provides a “sneak peak” into the future, including key features that empower Windows administrators to: Run commands on a remote computer, or better, against N other computers.  Use the new PSJob cmdlets to start remote jobs and retrieve the results, either individually or in-aggregate!  Write real cmdlets in PowerShell script itself!  Internationalize your scripts and their output, not to mention debugging those same scripts!

This CTP release helps developers to more easily layer their runtime or GUI on top of PowerShell, leveraging its cmdlets and remoting infrastructure.  It includes APIs to create and use a pool of Runspaces (engines) to run cmdlets.  This release also presents very early looks at Restricted Runspaces (the ability to declare a script, cmdlet or variable public or private) and the Graphical PowerShell (a script editor and a Unicode-enabled console).  These are just a few of the new features I think are interesting in Windows PowerShell 2.0 CTP.  Additionally this CTP includes some simple updates... like new parameters to select-string (Context, AllMatches, NotMatch and Encoding) and new operators like –split and -join!

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 CTP (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!

We hope you like where we’re headed with this release.  Help us get it right!  Tell us what is good and what is bad.  We have explicitly chosen to provide a public preview as early as possible to give us the best chance to incorporate feedback.

A CTP, by its very nature, is early code and thus WILL CHANGE by the final release.  It is explicitly not tested to the quality of a Beta in order to release it in a time frame that will give us a chance to act on feedback.  Even with those caveats, I hope you are pleased with results!  Try it out!

Download Windows PowerShell 2.0 CTP

Kenneth Hansen [MSFT]

Principal Lead Program Manager

Windows PowerShell

 

Release Highlights

This is a summary list of features added for the CTP of Windows PowerShell 2.0.  More descriptions are found in the "What's New in Windows PowerShell 2.0 CTP" link below, in the Release Notes and in the “about” files that ship with the release.

Ø  Compatibility with PowerShell 1.0

Ø  PowerShell Remoting

Ø  Background Jobs

Ø  ScriptCmdlets

Ø  Data-only Language

Ø  Script Internationalization

Ø  Script Debugging

Ø  New APIs for extracting Metadata from Commands and Parameters

Ø  New Parser Tokenizer API

Ø  New PowerShell Hosting APIs

Ø  Pools of Runspace

Ø  Restricted Runspaces

Ø  Graphical PowerShell

Ø  Out-GridView cmdlet

Additionally a number of improvements have been made to existing Cmdlets and capabilities, including:

Ø  Changes to TabExpansion function

Ø  New parameters added to Select-String

Ø  Updated Type Adapters

Ø  Improvements to Get-Member

Ø  Improved ADSI support

Ø  New parameters added to Get-WMIObject

Ø  Improved Bitwise Operators (int64)

For details checkout this blog: What’s New in Windows PowerShell 2.0 CTP

 

Submitting Feedback

As stated, the intent of this CTP is to get your feedback.  Please submit your feedback using the Connect Website (adding a CTP: to the title), posting on the Windows PowerShell Discussion Group, or commenting on the Windows PowerShell Blog.

Caveats

This software is a pre-release version.  It will not work the way a final version of the software does.  Features will change before final release.  See the blogs below and the Release Notes for further information on restrictions.

CTP != Beta !

Platform Requirements

Versioning

CTP: Watch this Space

 

Leave a Comment
  • Please add 8 and 4 and type the answer here:
  • Post
  • PingBack from http://msdnrss.thecoderblogs.com/2007/11/06/the-community-technology-preview-ctp-of-windows-powershell-20/

  • PowerShell v2.0 CTP is public ...

  • As anyone who reads this blog knows, I'm a big fan of PowerShell, the new shell and scripting language

  • When installing on XP SP2, if you get a prompt that says you need WS MAN, that WS-Management v1.1 (KB936059). Update details here: http://support.microsoft.com/kb/KB936059 and the update can be found at http://www.microsoft.com/downloads/details.aspx?FamilyID=845289ca-16cc-4c73-8934-dd46b5ed1d33&DisplayLang=en

  • I'm a Powershell fan (a recovering LogParser junkie - check out this mighty fine mix from MS.COM operations

  • I'm a Powershell fan (a recovering LogParser junkie - check out this mighty fine mix from MS.COM

  • Want to see the new featurs and functions of PowerShell as it marches to a 2.0 milestone? So do I! Compatibility

  • When I did get-alias kill, I used to get the name of the Cmdlet under Definition column, but PowerShell 2.0 CTP shows the type of the object and then Cmdlet name. I guess my console windows is not wide enough to show the whole Definition column, so I have to do "get-alias kill | ft -autosize" or "get-alias kill | fl"

    When I use get-alias Cmdlet, I care about what the actual Cmdlet name is the most. I don't really care about what the type of it. Is there any compelling reason the type had to be included?

  • The actual change was to snapin-qualify the cmdlet named by the alias. In V1, if someone created a function Get-ChildItem, then "dir" would call that command instead of the Get-ChildItem cmdlet. With this change, the correct cmdlet in the correct snapin will always be called (mod a couple of additional things we need to do to really fully qualify the path.) The change you're seeing to the output of Get-Alias is a side-effect. The current CommandInfo format description allocates 15 characters to the command type then splits the remaining space between the name and the definition. Since the name is typically only a few characters long, a lot of space is wasted. This is something we're looking at for a number of the types. For example, take a look at the output of Get-Help * and you'll also see a lot of wasted space.

    -bruce

    ==================

    Bruce Payette [MSFT]

    Principal Developer,

    Windows PowerShell

  • I'm writing this post from version 12.0.1366.1026 of Windows Live Writer - updated as part of Windows

  • Som jag skrev i mitt tidigare inlägg om PowerShell 2.0 (CTP) så går det alltså att ladda hem denna förhandstitt

  • The PowerShell team released a Community Technology Preview of PowerShell 2.0 this week. They have had

  • Seems that with 2.0 CTP commands that take flags that begin with -- have problems. Flags with two minus signs at the beginning must now be quoted or the double minus sign is stripped from the flag.

    Couldn't find any links to anywhere to report bugs. Maybe there will be when the 2.0 beta is released?

  • The PowerShell 2.0 CTP is here!

  • Will/Does powershell support tabs such as IE 7 tabs?  

Page 1 of 2 (20 items) 12