Now, I can work on the implementation of my new Module parameter and other details of my function. I didn’t have to worry about square brackets, matching parentheses, the exact names of the attributes (is that ParameterSet or ParameterSetName?), or anything other than my function.
I haven’t spent a minute fooling with syntax. (I can do this later, but I like to get a head start.) Then, I click OK.
Then, in the Parameters section, I assign each parameter to a parameter set.įinally, I add the starter help content and output type. I verify that the CmdletSet is selected as the default parameter set. Next, I add the parameter sets: CmdletSet for the Command parameter and ModuleSet for the Module parameter. I don’t need to think about syntax, just about my function. I click Enable Cmdlet Binding, add a Module parameter, set the types for my parameters, and make them mandatory. I don’t need to enter anything that I’ve already defined. The Function Builder parses the simple function. I right click my function and then click Edit Function. But, instead of looking up the syntax for parameter sets, I use the automation in PowerShell Studio 2014. The Command and Module parameters are exclusive, so I need two parameter sets. I still have a lot to do to make this function work correctly, but at this point, I realize that users might want the HelpUri values of all commands in a module. $cmd = Get-Command $Command -ErrorAction Silentl圜ontinue It’s actually stored in one of two places, but I want to keep this very simple. The HelpUri value is the online location of a help topic. I’ll start with a very simple function that gets the value of the HelpUri property of a command. The new Function Editor handles all of the syntax so I can concentrate on my function. Typically, I use snippets for the syntax, or search for an old function to use as a template (dir *ps1 | Select-String DefaultParameterSetName | Select FileName –Unique).īut, in PowerShell Studio, I don’t have to remember any of it. I wrote the about_Function help topics that explain the syntax of these elements, but I still never remember them. The syntax for parameter sets and a default parameter set, which requires the CmdletBinding attribute, is tricky.
And, thinking about errors and the user experience often leads me to add parameter sets. I might even start with fixed values to test the concept and, after testing, convert them to parameters. When I write functions, I often start with the basic command – the one that makes the function work – and then build in features. In this post, I learn to use the Function Editor in PowerShell Studio. The complex syntax of parameter sets in functions is one of those cases. But, as the command line becomes more complex, we need tools to restore our efficiency. Like many of you, I really live at the command line, because automation is more efficient than single actions.
0 kommentar(er)
