PowerShell Team
Automating the world one-liner at a time…
Latest posts
Get Localized PowerShell Help Files
The Windows PowerShell core help files that were included in Windows 7 RTM were localized into ten languages. You can download the XML and TXT versions of these localized files and use them in your Windows PowerShell projects. The Windows PowerShell core help files are localized into the following languages: · de-de (German-Germany) · es-es &...
PDC09 SVR12 and SVR13 Slides
Slides for the two PDC 09 sessions - SVR12 and SVR13 attached. Enjoy Cheers Nana [MSFT] --- Narayanan Lakshmanan [MSFT] DeveloperVisit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx Slides.zip
The PowerScripting Centennial
99 podcasts of Pure Power. That’s what the PowerScripting Podcast has been churning out for almost three years! Well, this week is extra special, as you might imagine from the title of this post. On Thursday, they record episode one hundred: a huge milestone by any means. A testament to dedication and passion. Episode #100 looks like it’s going to be fun: tips, tricks, and who knows what else. Join em’ live on UStream if you want to be part: Come check out our live video stream as we record the show! We usually air every Thursday at 9:30pm EST (GMT-5), unless otherwise noted on our blog. (Live video) (add to...
Use The Right Version of PowerShell.
A number of recent problems that users have reported can be tracked down to using incorrect versions of PowerShell. Tobias Weltner (of PowerShell Plus fame) blogged the details of issue and want you need to do to ensure you are running the right copies. The blog title is Are you using the correct PowerShell version? You should definitely check this out. Experiment! Enjoy! Engage! Jeffrey Snover [MSFT] Distinguished Engineer Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http:...
PowerShellHostVersion – WTF?
Superstar Shay Levy recently wrote a blog article, Module Manifest Gotcha . He was exploring the various options that the Module Manifest provides and saw what he thought was a problem with using the PowerShellHostVersion key. PowerShellHostVersion key Specifies the minimum version of the Windows PowerShell host program that works with the module. The “gotcha” here is that there are LOTS of PowerShell Hosts: PowerShell.exe, Powershell_ISE.exe, PowerGUI, Sapien’s PrimalScript, PowerShellPlus and others (apologizes in advance to those I forgot to mention). Shay created a manifest with...
Get Great Software and Help Haiti
I’m always impressed by the level of creativity of the people in the PowerShell community. I remember having my socks knocked off the first time I saw what SoftwareFX did with PowerGadgets. I could not believe the things that they were doing. In fact I couldn’t even figure out how they were doing some of them! Well the superstars at SoftwareFX have engaged their creative sides once again, this time to help Haiti. They have just announced the PowerShell Haiti Relief Offer where they are offering a copy of PowerGadgets for 50% off and will contribute all the money to organizations he...
How objects are sent to and from remote sessions
Instead of piping unstructured text, Windows PowerShell pipes objects between commands in a pipeline. As a consequence PowerShell remoting also deals with objects when passing data to and from remote sessions. This post explains how remote objects are serialized and which types of objects can be sent with full fidelity. You might want to refer to this post when passing arguments to remote commands or when designing remoting-friendly cmdlets or functions. Property bags You might have noticed “Deserialized” prefix in front of type names of some objects received from a remote session: Objects ...
TB & PB
“To ship is the choose.” That is the sad reality behind a number of the things that we regretted about V1. When we first started the project (a LONG time ago) we knew that we wanted to close the semantic gap between what admins thought and what they had to type. Imagine that you wanted to find all the processes that had greater than 15MB of workingset. Who the heck could type in the following: PS> Get-Process |where {$_.Workingset –ge ?????} What? You didn’t know that 15MB was 15728640 bytes? Yes you should have written: PS> Get-Process |where {$_.Workingse...
TB & PB
“To ship is the choose.” That is the sad reality behind a number of the things that we regretted about V1. When we first started the project (a LONG time ago) we knew that we wanted to close the semantic gap between what admins thought and what they had to type. Imagine that you wanted to find all the processes that had greater than 15MB of workingset. Who the heck could type in the following: PS> Get-Process |where {$_.Workingset –ge ?????} What? You didn’t know that 15MB was 15728640 bytes? Yes you should have written: PS> Get-Process |where {$_.Workingse...