MOSS MVP

I've moved my blog to http://blog.falchionconsulting.com!. Please update your links. This blog is no longer in use--you can find all posts and comments at my new blog; I will no longer be posting to this site and comments have been disabled.

Thursday, August 20, 2009

Attend the SharePoint Conference 2009 for Free!

ShareSquared, Inc. and Kodak just announced a contest where you can win a free pass to the 2009 SharePoint Conference and four nights stay at Mandalay Bay in Vegas!  You can also win some free consulting or a Kodak scanner!  Visit http://www.sharepointgiveaway.com/ for more information and to enter to win - good luck!

BTW, I'll be at the conference as well so look me up if you're there!

Saturday, August 1, 2009

Setting PowerShell Switch Parameters Dynamically

I've been doing a lot of configuration driven PowerShell scripts lately and I had a bit of trouble figuring this bit out so I thought I'd write up a short post about it.  A lot of the cmdlets that I've been working with take in switch parameters and I needed a way to set those parameters dynamically based on settings in a configuration file.  For those new or unfamiliar with PowerShell, switch parameters are just parameters that don't have any corresponding value.  Here's an example:

Get-Command -Name Start-Sleep -Syntax

The "-Syntax" parameter above is a switch parameter - it takes no value and simply tells the Get-Command cmdlet to return only the syntax of the command.  This particular cmdlet isn't the best example of where you would want to set the parameters dynamically but you get the idea.  So how would you set the -Syntax parameter dynamically?  Here's an example:

[xml]$config = Get-Content .\Configurations.xml
Get-Command -Name Start-Sleep -Syntax:([bool]::Parse($config.Settings.ShowSyntax))
You can imagine an XML structure where there may be some kind of configuration settings (in this case: <Settings ShowSyntax="true" />).  So you basically just add a colon (:) after the parameter and then provide a Boolean value; in this example because the value is in the form of an XmlElement we have to convert it to a Boolean.
This is one of those simple things that really pissed me off because it took forever for me to figure it out so I figured I'd share this simple tip with others (if you're a SharePoint person you'll want to know about all this stuff for the next version - believe me!).