PowerShell Community Extensions 1.1.1 Released!

It took a little while but we finally got a lot of the issues resolved that you reported in PSCX 1.1.  Tonight (well *early* this morning) I released PSCX 1.1.1.  This release is a primarily a maintenance release.  It fixes about 30 defects and adds five new features.  You can download 1.1.1 from here.  You will need to uninstall any previous version you have of PSCX before you can install 1.1.1.  We really thought we had the VS 2005 Setup project configured to do an upgrade and it "seemed" to work.  However further testing revealed that sometimes it would not re-register the updated PSCX snapin with PowerShell.  Then PowerShell gets upset because the version number of the snapin doesn’t match what has been registered with PowerShell.
 
Here is the final list of changes in 1.1.1:

NEW CMDLETS

  • Get-ExportedType

NEW FUNCTIONS AND FILTERS

  • Collect
  • Elevate

NEW SCRIPTS:

  • Get-ViewDefinition.ps1
  • Out-Speech.ps1
  • Select-Random.ps1

NEW VARIABLES

  • $RegexLib

NEW ALIASES

  • su (Elevate)

Other changes include the new -PageSize parameter on Get-ADObject.  Select-Xml now outputs XPathDocumentNavigator objects instead of strings.  There is also a new elevate function (alias su) that will invoke the UAC elevation UI on Vista and the RunAs dialog box on XP.  For example:

elevate
elevate notepad c:\windows\system32\drivers\etc\hosts
elevate gci c:\windows\temp
elevate {gci c:\windows\temp | export-clixml tempdir.xml; exit}
elevate {gci c:\windows\temp | export-clixml tempdir.xml; exit} |
        %{$_.WaitForExit(5000)} | Import-Clixml tempdir.xml

Also if you ever wonder what other views are available for a particular object, try this:

23> Get-ViewDefinition ‘System.Diagnostics.Process’

Name       : Priority
Path       : C:\Windows\System32\WindowsPowerShell\v1.0\DotNetTypes.format.ps1xml
TypeName   : System.Diagnostics.Process
SelectedBy : System.Diagnostics.Process
GroupBy    : PriorityClass
Style      : Table

Name       : StartTime
Path       : C:\Windows\System32\WindowsPowerShell\v1.0\DotNetTypes.format.ps1xml
TypeName   : System.Diagnostics.Process
SelectedBy : System.Diagnostics.Process
GroupBy    :
Style      : Table

Name       : process
Path       : C:\Windows\System32\WindowsPowerShell\v1.0\DotNetTypes.format.ps1xml
TypeName   : System.Diagnostics.Process
SelectedBy : System.Diagnostics.Process
GroupBy    :
Style      : Wide

On the download page for PSCX 1.1.1 you will be able to see the details on all the work items that went into this release.

I would like to acknowledge and thank the following developers who helped out with the 1.1.1 release: Oisin Grehan, Richard Lehrbaum and Burt Harris!

Please be sure to keep those work item submissions coming.  I can’t promise that we will get the next release out any sooner but we do take defects seriously.  And we do appreciate all the folks out there that have been using PSCX and contributing by submitting work items and participating in the discussion forums on the PSCX CodePlex site.


Keith Hill
PSCX Project Coordinator
Windows PowerShell MVP

About these ads
This entry was posted in PSCX. Bookmark the permalink.

3 Responses to PowerShell Community Extensions 1.1.1 Released!

  1. Unknown says:

    Keith, I came to your site because of the PCX update, which is great.
     
    Just one quibble: my browser of choice, minefield, refuses to display your page because the DTD isn\’t coded properly.
     
    http://validator.w3.org/check?uri=http%3A%2F%2Fkeithhill.spaces.live.com%2Fblog%2F&charset=%28detect+automatically%29&doctype=Inline&ss=1
     
    You have:
     
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
     
    but no DTD following the declaration
     
    It\’s true, I think, for all "spaces" pages, but anything you could to to complain would help. Thanks!
     
     
     
     
     

  2. Keith says:

    I\’ve submitted that feedback.  You might want to do the same via the "Feedback" link at the bottom right of this page.

  3. Sean says:

    I downloaded PSCX because it looked easy and it had the get-TerminalSession cmdlet that I wanted to use.  It works locally, but when I try to access a remote box with it, it tells me "A security package specific error occurred.  I\’m an admin on both the local and remote boxes.  What setting do I need to change to make this work remotely?
    Thanks.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s