Note <\/b>I am not going to be able to explain all of this to everyone’s fullest satisfaction. It is a bit complicated. But hopefully, I will explain it well enough that you can copy my script and modify it to do other things. So in effect, what I hope to create is a dynamic parameter template that you can use to create powerful and useful scripts. This is cool stuff, and for me, it is worth the effort. Also note that you do not have to do this. You can easily use available tools that will populate a WinForm with a drop-down list of available printers. Part of the point of today’s post is to show you how you can do this. If you choose to do it is entirely up to you. Hope you enjoy the post as much as I had fun writing it.<\/p>\n
When I use the Param<\/b> statement to add parameters to a function, I am accepting input that will change the way the function works. Typically, I use parameters to permit me to change the target of a function, and I call the ComputerName<\/b> parameter as shown here:<\/p>\n
Function example<\/strong><\/p>\n {<\/p>\n Param([string]$computername)<\/p>\n }<\/p>\n I can also set default values for a parameter, which gives me a default behavior for my function. Typically, I like to target a function on my local computer. I like to obtain this value from the environmental variables as shown here:<\/p>\n Function example<\/strong><\/p>\n {<\/p>\n Param([string]$computername = $env:computername)<\/p>\n }<\/p>\n But what if I wanted to produce a list of available computers that might be on my target network? This would require running a script block, and unfortunately I cannot do this. I need a dynamic parameter.<\/p>\n Here is what I need to do to create a dynamic parameter:<\/p>\n I need to create a ParameterAttribute<\/b> object. To do this, I use the New-Object<\/b> cmdlet, and then I create a ParameterAttribute<\/b> object. This class resides in the System.Management.Automation namespace. (This is the namespace that contains all of the Windows PowerShell stuff). I store the newly created object in a variable named $attributes<\/b>.<\/p>\n Now I want to specify a name for the parameter set. This is a straight-forward value assignment to the ParameterSetName<\/b> property. I decide to call it __ParameterSets<\/b>. I also decide to make the attribute mandatory. Here are the three lines of script that accomplish this task:<\/p>\n $attributes = new-object System.Management.Automation.ParameterAttribute<\/p>\n $attributes.ParameterSetName = "__AllParameterSets"<\/p>\n $attributes.Mandatory = $true<\/p>\n Now I need to create an attribute collection so I have a place to put the attributes that I just created. I use the New-Object<\/b> cmdlet again, and this time, I store the returned attribute collection object in the $attributeCollection<\/b> variable. The collection object comes from the System.Collections.ObjectModel namespace, and I specify that it will be of the [system.Attribute]<\/b> type. When I have the object, I add my attributes to it by calling the Add<\/b> method. This script is shown here:<\/p>\n $attributeCollection =<\/p>\n new-object -Type System.Collections.ObjectModel.Collection[System.Attribute]<\/p>\n $attributeCollection.Add($attributes)<\/p>\n I need to get my collection of printer names. I use the Get-CimInstance<\/b> cmdlet to query the Win32_Printer WMI class, and I return only the Name<\/b> property. I store these printer names in the $_Values<\/b> variable.<\/p>\n Now I create another object. This time it is the ValidateSetAttribute<\/b> object. Again, this comes from the System.Management.Automation .NET Framework namespace. When I am creating the ValidateSetAttribute<\/b> class, I specify the printer names stored in the $_Values<\/b> variable. I store the returned ValidateSetAttribute<\/b> object in the $validateSet<\/b> variable. I pass this object to the Add<\/b> method of the AttributeCollection<\/b> object that I created in the previous step. Here is the script that does this:<\/p>\n $_Values = (Get-CimInstance win32_Printer).name <\/p>\n $ValidateSet =<\/p>\n new-object System.Management.Automation.ValidateSetAttribute($_Values)<\/p>\n $attributeCollection.Add($ValidateSet)<\/p>\n Whew…<\/p>\n I still have not created everything I need to permit me to create my dynamic parameter. I need to create two more objects, and finally I will be done. I now use the New-Object<\/b> cmdlet to create a RuntimeDefinedParameter<\/b>. When I do this, I need to tell it the name of the parameter. In this example, it is Printer<\/b>.<\/p>\n I also need to tell it where to find the potential values. The values come from the $attributeCollection<\/b> variable. I store the RunTimeDefinedParameter<\/b> in the $dynParam1<\/b> variable. Here is the script that accomplishes this task:<\/p>\n $dynParam1 =<\/p>\n new-object -Type System.Management.Automation.RuntimeDefinedParameter(<\/p>\n "Printer", [string], $attributeCollection)<\/p>\n The last object I need to create is the RuntimeDefinedParameterDictionary<\/b>. Once again, this dictionary object comes from the System.Management.Automation .NET Framework namespace. I add the name of Printer<\/b>, and the RuntimeDefinedParameter<\/b> object that I stored in the $dynParam1<\/b> variable.<\/p>\n Now it is time to return the RuntimeDefinedParameterDictionary<\/b> object that I stored in the $paramDictionary<\/b> object, so I call the Return<\/b> keyword and pass the $paramDictionary<\/b> variable as shown here:<\/p>\n $paramDictionary =<\/p>\n new-object -Type System.Management.Automation.RuntimeDefinedParameterDictionary<\/p>\n $paramDictionary.Add("Printer", $dynParam1)<\/p>\n return $paramDictionary }<\/p>\n At this point, it is just a regular advanced function. I add a Begin<\/b> and a Process<\/b> section to the function. I am not doing anything special in the begin section, and the process section is where I place my script block. Following the script block, I have my End<\/b> section. This is shown here:<\/p>\n begin {}<\/p>\n process {<\/p>\n $printer = $PSBoundParameters.printer<\/p>\n Invoke-CimMethod -MethodName printtestpage -InputObject ( Get-CimInstance win32_printer -Filter "name LIKE '$printer'") }<\/p>\n end {}<\/p>\n }<\/p>\n When I run the function, I am presented with a nice drop-down list that permits me to select a printer. This is the dynamic portion of the parameters is shown in the following image:<\/p>\n To me, it is worth a little bit of extra script to enable this functionality. Here is the complete script:<\/p>\n Function out-TestPage {<\/p>\n [CmdletBinding()]<\/p>\n Param()<\/p>\n DynamicParam {<\/p>\n $attributes = new-object System.Management.Automation.ParameterAttribute<\/p>\n $attributes.ParameterSetName = "__AllParameterSets"<\/p>\n $attributes.Mandatory = $true<\/p>\n $attributeCollection =<\/p>\n new-object -Type System.Collections.ObjectModel.Collection[System.Attribute]<\/p>\n $attributeCollection.Add($attributes)<\/p>\n $_Values = (Get-CimInstance win32_Printer).name <\/p>\n $ValidateSet =<\/p>\n new-object System.Management.Automation.ValidateSetAttribute($_Values)<\/p>\n $attributeCollection.Add($ValidateSet)<\/p>\n $dynParam1 =<\/p>\n new-object -Type System.Management.Automation.RuntimeDefinedParameter(<\/p>\n "Printer", [string], $attributeCollection)<\/p>\n $paramDictionary =<\/p>\n new-object -Type System.Management.Automation.RuntimeDefinedParameterDictionary<\/p>\n $paramDictionary.Add("Printer", $dynParam1)<\/p>\n return $paramDictionary }<\/p>\n begin {}<\/p>\n process {<\/p>\n $printer = $PSBoundParameters.printer<\/p>\n Invoke-CimMethod -MethodName printtestpage -InputObject ( Get-CimInstance win32_printer -Filter "name LIKE '$printer'") }<\/p>\n end {}<\/p>\n }<\/p>\n Join me tomorrow when we will have more cool Windows PowerShell stuff.<\/p>\n I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n Ed Wilson, Microsoft Scripting Guy<\/b> <\/p>\n","protected":false},"excerpt":{"rendered":" Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use dynamic parameters to populate a list of printer names. Microsoft Scripting Guy, Ed Wilson, is here. Using a Windows PowerShell function to send a test page to a printer is pretty cool (see Use PowerShell to Send Test Page to a Printer). But it would […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[491,404,3,4,45],"class_list":["post-1795","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-printers","tag-printing","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use dynamic parameters to populate a list of printer names. Microsoft Scripting Guy, Ed Wilson, is here. Using a Windows PowerShell function to send a test page to a printer is pretty cool (see Use PowerShell to Send Test Page to a Printer). But it would […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/1795","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=1795"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/1795\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=1795"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=1795"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=1795"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Create ParameterAttribute object<\/h2>\n
Create attribute collection<\/h2>\n
Create validation set<\/h2>\n
Create RuntimeDefinedParameter<\/h2>\n
Create RuntimeDefinedParameterDictionary object<\/h2>\n
Dude, it is a regular advanced function<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/hsg-3-21-14-01.png\" "\\"Image")
<\/a><\/p>\n