Syntax coloring for programming languages was originally introduced as a visual aid to assist developers in assessing the syntactical correctness of code. Unlike the squiggly red or green underlines in Microsoft Word colors indicate validation rather than error. So while glancing at a syntax colored stretch of code the usual green hue of comments and […]
Tag: cmdlet
iPowerShell comes to iPad
With the recent successful launch of iPowerShell v2 for iPhone and iPod touch, we have turned our attention to another platform, the Apple iPad. After a month of diligent work, we are pleased to announce that iPowerShell v2.1 will be released to the app store in early April May as a universal app. This single […]
Extending PrimalSense for external PowerShell snapins
Getting PrimalSense for a COM object that you didn’t have installed on your development machine is fairly simple: Copy the TLB file (type library) to you machine, associate it to a progid and you are all set. With PowerShell Cmdlets it is not quite that easy. Say you have to use a snapin that is […]
ChangeVue to get PowerShell cmdlet interface
ChangeVue 2009, SAPIEN Technologies’ source control system, is about to get a new way to manage its content: a PowerShell snap-in! That’s right. You will soon be able to manage your existing ChangeVue repositories directly through the PowerShell console or through a PowerShell script. Simply install the ChangeVue snap-in using the PowerShell cmdlet “Add-PSSnapin -name […]
Managing Active Directory with Windows PowerShell – IN PRINT!
Yes, its finally true. You can finally get your hands on Managing Active Directory with Windows PowerShell: TFM. The book is being printed so you can get your copy today. You can order it today at ScriptingOutpost.com in both print and ebook format. Or if you prefer the best of both worlds get both as a bundle.
More Fun with History
I blogged a few days ago about taking advantage of PowerShell’s history. As I was looking at the history object I noticed the ExecutionStatus property. Most of the time it should be “completed”. But what about commands that failed? Why not search my history buffer?
Fun with History
In the Pixar film Cars, Mater demonstrates to Lightning McQueen how to drive backwards. Lightning is astounded. Mater explains, “Don’t need to know where I’m going as long as I know where I’ve been.” Probably not the exact quote but the point is if you know what you’ve done or where you’ve been it makes it very easy to know where you’re going or what to do next. In PowerShell you can take advantage of the shell’s history objects to speed up what you want to do next.
List PowerShell verbs
As you may be aware, PowerShell cmdlets are supposed to be named with a standard verb. I usually suggest that scripters name scripts and functions also using a standard verb, although it is not required and I certainly bend the rules from time to time. Hopefully by now you’re saying to yourself, “Show me the verbs!”
Quest AD Cmdlets 1.1 Beta Now Open to the Public
Quest Software and the PowerGUI team have been quietly working on a private beta of the new version of their popular and effective cmdlets for managing Active Directory. That process has completed and the beta is now open to the public
Scriptblocks as Cmdlet Parameter Values
Jeffrey Snover explains how scriptblocks can become the value for ANY cmdlet parameter. http://blogs.msdn.com/powershell/archive/2008/04/21/mindwarpingpower-cmdlets-scriptblock-parameters.aspx#comments
