The param()’s looks very promising, especially now that I’m branching off from simple straight up PS scripting to making libraries of code to handle things.

Help comments handled by the shell?! No way! Another reason I can’t wait for V2!

Thanks for the pointer on XML, however I went this route as I wanted to have the version.xml file as human readable as possible (and it was a fun challenge to learn about System.XML). I don’t know if Export-clixml has changed with V2, but I find that V1 has bloat that could be forgotten when updating the file by hand. Perhaps if I had a UI or another script that handled updating version.xml I would go that route. (I could however see that export-clixml could be used for the local version.xml!)

Thanks again! It’s quite an honor to be critiqued by you!

-Josh Erickson

- The param() statement is the ideal way to define script parameters. When you define a parameter through a param statement, you only need to type as much of the parameter name required to disambiguate it from other parameters.

PS:34 > function foo { param([switch] $help) if($help) { “Help!” } }

PS:35 > foo -h
Help!

- You might find Import-CliXml / Export-CliXml to be easier data structures to deal with (rather than digging through XML)

PS > $versionInfo = @{ Version = 1.0; File = “http://foo” }
PS > Export-Clixml -In $versionInfo -Path version.xml
PS > $versionInfo = Import-CliXml version.xml
PS > $versionInfo.Version
1

PS > $versionInfo.File
http://foo

- You might consider formatting your help instead as help comments. We intentionally designed them to work in V1, but light up in V2: http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx

Hope this helps,

Lee Holmes [MSFT]
Windows PowerShell Development