dynamicparam Support

[bgleason]

To help you better we need some information from you.

*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***

Product: PowerShell Studio 2020 (64 Bit)
Build: v5.7.174
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.18363.0

*** Please add details and screenshots as needed below. ***

Is there any plan for PSS to support dynamicparam. I see that question was kind of asked some time ago:
viewtopic.php?p=60862#p60862

Code: [Select all] [Expand/Collapse] [Download] (Untitled.ps1)

1.   dynamicparam {
2.     if ($ScaleMethod -eq "AutoStatic") {
3.       $attThreashold = New-Object System.Management.Automation.ParameterAttribute
4.       $attThreashold.Mandatory = $true
5.       $attributeCollection = New-Object System.Collections.ObjectModel.Collection[System.Attribute]
6.       $attributeCollection.Add($attThreashold)
7.       $paramThreshold = New-Object System.Management.Automation.RuntimeDefinedParameter('Threshold', [Int], $attributeCollection)
8.       $paramDictionary = New-Object System.Management.Automation.RuntimeDefinedParameterDictionary
9.       $paramDictionary.Add('Threshold', $paramThreshold)
10.       return $paramDictionary
11.     }
12.   }

Didn't really go anywhere it seems... To reiterate the prior post, ISE Supports it, just wondering what the challenges are in PSS, if any...?

Thanks!!

DO NOT POST LICENSES, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM

[Alexander Riedel]

Well, it is basically a chicken - egg problem. The parameters, the name 'dynamicparam' implies, are defined at runtime. So nobody can know what the parameters will be until the script runs. We do not run your script just to determine such things, that would be a huge security hole.
Even if (and that would be a bad idea) we would use the data from the last execution of the script, there is no guarantee whatsoever that conditions would be the same, resulting in the same set of dynamic parameters.
So I am not quite sure what you mean by 'supporting' this. Can you please elaborate?

[bgleason]

Without providing more images, I will try to provide context...

When you are coding in the PSS ide, you can see my -ScaleValue and -ScaleMethod are detected parameters for the function/cmdlet I am calling, and you parse those the moment they are created and the file is saved, it is like PSS, parses through and says, "Yep, for the function I see, those are valid parameters", but it does not do that for dynamicparams... For ex. if you are typing your function, "Doing-Something" followed with a "-" to list your available parameters, only the "params" values are available... Now if I was working in ISE as my IDE, it does support the parsing of dynamicparm values where if I was to bring us a parameters list by typing the "-" after my function name, it would be listed...

Actually, added the images.. The thing that is interesting is also how ISE is showing CMDletBindings re. WhatIf and Confirm, where PSS is not...

[Alexander Riedel]

Check if the ISE shows your dynamic parameters just after you launched it or only after you ran that script at least once please.

[bgleason]

Sorry for the late reply...

I open a fresh instance of ISE, copy my code out of PSS, paste it into ISE and my dynamicparam is supported without having to save or run the script...

Thanks,

Brian

[bgleason]

I saw today that -WhatIf and -Confirm, sorry about that miss, they are just down at the bottom of the params list, still not supporting dynamicparam though..

Thanks,

Brian

[bgleason]

Anything further on this...??

[Alexander Riedel]

We have added it to the list of things to do. I honestly cannot tell you when this will be looked at, it will not be next week though.