-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot set the Value property for PSMemberInfo object of type "System.Management.Automation.PSParameterizedProperty" #11837
Comments
Possibly related (though there it is about not using /cc @daxian-dbw |
Yes, similar to the referenced issue, this one is also because the |
The problem applies only (?) to @mklement0I I think it's not possible to use properties like |
Indeed; fixing this limitation is what the previously linked #4554 is about. |
Worth noting (since it isn't obvious) that that's due to Value being a parameterized property and Value2 being a normal property. |
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
2 similar comments
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes. |
Steps to reproduce
Expected behavior
Actual behavior
Environment data
Notes
Value getter does not work too.
But calling
InvokeSet
orInvokeGet
explicitly on item's value works fine, e.g.:Powershell 6.2.4 affected by this bug also. Powershell 5.1.18362.145 works fine.
The text was updated successfully, but these errors were encountered: