Windows Management Framework 3.0 Community Technology Preview (CTP) #2 Available for Download

Windows Management Framework 3.0 Community Technology Preview (CTP) #2 Available for Download

Rate This
  • Comments 16

 

I’m pleased to announce that the Community Technology Preview #2 (CTP2) is available for download.

Windows Management Framework 3.0 CTP2 makes some updated management functionality available to be installed on Windows 7 SP1 & Windows Server 2008 R2 SP1. Windows Management Framework 3.0 contains Windows PowerShell 3.0, WMI & WinRM.

IMPORTANT: If you have WMF3.0 CTP1 installed, you must uninstall it before installing CTP2.

Overview of changes since WMF 3.0 CTP1
1. Customer Reported Bug Fixes
Many customer reported bugs have been fixed since the WMF 3.0 CTP1. The release notes contains a list of bug titles, but please check Connect for full details.

2. Single Command Pane in Windows PowerShell ISE
The Command and Output panes in Windows PowerShell ISE have been combined into a single Command pane that looks and behaves like the Windows PowerShell console.

3. Updatable Help
The WMF 3.0 CTP1 release notes described a new Updatable Help system in Windows PowerShell 3.0 and included a copy of the help content. The Updatable Help system is now active on the Internet. To download and update help files, type: Update-Help.

4. Windows PowerShell Workflows
A number of enhancements have been made in the scripting experience for Windows PowerShell Workflows, including new keywords: Parallel, Sequence & Inlinescript. A document describing these changes will be published to the download page shortly.

5. Remote Get-Module
The Get-Module cmdlet now supports implicit remoting. You can now use the new PSSession and CIMSession parameters of the Get-Module cmdlet to get the modules in any remote session or CIM session. A number of other module enhancements are listed in the release notes.

Feedback & Bugs
We welcome any feedback or bug submissions to the Windows PowerShell Connect site: http://connect.microsoft.com/PowerShell

Additional Information:
This software is a pre-release version. Features and behavior are likely to change before the final release.

This preview release is designed to enable the community to experience and review the preliminary designs and direction of key features Windows PowerShell 3.0 and to solicit feedback before features are finalized.

For an interesting post describing what to expect with a CTP, read this very old post from Jeffrey

 

Travis Jones [MSFT]
Program Manager – Windows PowerShell
Microsoft Corporation

Leave a Comment
  • Please add 6 and 7 and type the answer here:
  • Post
  • Still no Vista support. Connect is just for namesake. No feedback actually is listened to.

  • I skipped CTP1; this time I gave it a try:

    1. PowerShell 3 look very nice.  Thanks!

    2. However, it takes a really long time to start (even with a SSD, after all assemblies were ngen-ed, and a very simple $profile, that's still about 10s).  Why is it so slow?

    3. Have you considered retaining the colors from syntax highlighting for previous commands in the Console pane?

  • @vistasp2: Actually, Connect is monitored quite a bit.  I would prefer that Microsoft concentrates on the newer OSs, before looking at older systems.  Once v3 is officially release, I would expect them to release shortly thereafter, an update for all currently supported OSs.

  • 1. Will the ISE support plug-ins / extensions?

    2. Will the self-hosting API change for .NET applications to self-host PowerShell scripts?

  • Does PowerShell 3.0 support the Dynamic Language Runtime features of .NET 4? example, I expect the following to work (it doesn't work in PS 2.0, nor does it support DynamicObject subclasses, dynamically that is)

    >$o = new-object System.Dynamic.ExpandoObject

    >$o.AnInt = 2

    >$o.AString = 'sometext'

    >$o.AnInt

    2

    >$o.AString

    sometext

  • @Eric: Check the download link for an ISE PDF.

  • Androticus - Your snippet should work but there was a bug in this preview package preventing it. It's been fixed.

  • Is SP1 absolutely needed for Win7 installation? Unfortunate use case: we have a few machines that cannot be upgraded to SP1 for some reasons (weird reasons, but we can do nothing about them).

  • this is awesome! is there documentation on how to expose cmdlets through webservices? i am really interested in trying out this feature but i don't know where to start.

  • @Roman - Yes, SP1 is required. You will get a "This update does not apply" error message if you try to install on Win 7 without SP1.

    @foureight84 - There is a doc on MSDN that walks you through exposing cmdlets through webservices here: archive.msdn.microsoft.com/mgmtODataWebServ. Also a good post in the PowerShell Magazine www.powershellmagazine.com/.../powershell-vnext-web-service-entities

  • Well, I dared to install it and now anything I type+enter rezults in a lot a red stuff on the screen. While Posh 2 worked very well. A small example:

    PS C:\Users\dsfgsdfgs> Get-ChildItem d:\ -Recurse | Where-Object{$_.Length gt 50

    0Mb}"System.String" to type "System.Type".

    writeErrorStream      : True

    Exception             : System.Management.Automation.ParentContainsErrorRecordE

                           xception: At line:1 char:53

                           + Get-ChildItem d:\ -Recurse | Where-Object{$_.Length

                           gt 500Mb}

                           +

                           ~~

                           Unexpected token 'gt' in expression or statement.

    TargetObject          :

    CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException

    FullyQualifiedErrorId : UnexpectedToken

    ErrorDetails          :

    InvocationInfo        : System.Management.Automation.InvocationInfo

    ScriptStackTrace      :

    PipelineIterationInfo : {}

    PSMessageDetails      :

    Nice isn't it?

  • I see some references to the new WPF add-on model for the ISE in the documentation, but I can't find any source code.  The doc refers to ISESimpleSolution and WatchWindow add-ons and says to look at their source for stuff like what interface to implement.  Any clues on where to get this sample code?

  • After installing the CTP on my Windows 7 machine, which is running SharePoint Server 2010, I get the following error message from SharePoint Management Shell (Powershell): "Microsoft SharePoint is not supported with version 4.0.30319.239 of the Microsoft .Net Runtime." Is there a workaround?

  • Installing this on a server that runs SharePoint leaves SharePoint Management Console unusable, due to incompatible .NET version. Is there a workaround?

  • FJ & Frank - Thanks for reporting the error with the SharePoint Management Shell. We will investigate and report back what we find.

Page 1 of 2 (16 items) 12