PowerShell v3

Share This Article

    Ooooh, ooooh.. it’s PowerShell v3.

    Now I’ve been looking at and reading blogs about PowerShell v3, which at this point is at CTP3.  And those blogs, and the documentation make it sound pretty dry and dusty.  So, I decided to install CTP 3 on a virtual machine.  That way, if things went bad, I could have a snapshot to revert to.  And, since I already had some VM’s  with PowerShell v2, and v3 is an update of v2, I already had a good starting point.

    There is a fair bit of documentation and a good help file on installing v3.  I started here: http://social.technet.microsoft.com/Forums/en-US/ITCG/thread/4807949e-58e6-4533-b35d-580d938dfbb2.  PowerShell is part of the Windows Management Framework 3.0 and the RC version is now available.  You can get the files here: http://www.microsoft.com/en-us/download/details.aspx?id=29939.  You will need to meet the prereq’s, and have .NET 4.0 installed, and then you can install the appropriate file.   My VM needed the Service Pack, and then I could install the .NET 4.0 update, followed by the WMF 3.0 file.  And then… YES!  I have v3!

    But, of course, it’s never quite that simple is it?  When I clicked on the icon to open the ISE, I could tell it was a different GUI.. there was a different splash screen.  Then I got the popup which said something to the effect that to get help files, run update-help, do you want to do this now?  I foolishly said no, so I don’t know if it would have worked.  But, when I went to run a simple get-help command, it told me the files weren’t available, run get-help with -online, OR download the help files.

    Now, I don’t want my VM connected to the internet all the time, so I didn’t want to use online help.  So, I chose to run update-help to download the files. After reconnecting the external network adapter, I ran update-help.   And, it’s so cool, there now is intellisense, so when you type ‘update-help’  followed by a dash, it gives you the list of parameter options.   Some blogs I had read said run update-help.  I did. That didn’t work.  The PowerTip of the Day from PowerShell.com, (one of my favorite things to get in email), said run the following: update-help -force -uiculture en-us.  That didn’t work either.  It wasn’t until I read a blog by Keith Hill that casually mentioned ‘run in an elevated prompt’ that I got it to work.

    Another blog included the handy tip was to run the following:  get-module | update-help -force -uiculture en-us.  That makes sure that it looks for help files for all the available modules.  Of course, some of your modules might be third party, and may not have help files or they may not be found.  You actually get a good error message saying which modules didn’t get help files.   See the screen shot below to see the messages I got after running ‘update-help -force  -uiculture en-us’:

    Once I had gotten those, I then was able to turn off internet access for my vm – once again disconnecting the external adapter.

    Looking at the menu, you can choose to turn command add-on off or on, and turn outlining off/on.

    I haven’t mentioned some of the other immediately obvious changes.  They’ve done away with the output window in the ISE as well, by having the output go to the command pane.  They’ve added a command pane, which shows you the cmdlets. The cmdlets can be filtered by module, or you can see all cmdlets.

    Then if you ask about the new features of v3:  Get-help about_


    So then I go, oooh, oooh.. disconnected sessions!  What are those cmdlets?

    I’ll continue with my raving about v3 in part two of this 3 part series on new features in PowerShell v3…

    Share This Article

      Related Articles:

      No comments yet.

      Leave a Reply

      Powered by WordPress. Designed by Woo Themes