Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove unimplemented parameters from Set-AuthenticodeSignature
See original GitHub issueSummary of the new feature/enhancement
Set-AuthenticodeSignature and Get-AuthenticodeSignature are both derived from the base class SignatureCommandsBase. The parameters are defined in the base class but implemented in the cmdlet class. Get-AuthenticodeSignature implements the SourcePathOrExtension and Content parameters, but Set-AuthenticodeSignature does not.
The problem is that Get-Command shows that parameters even though they are not implemented, causing confusion to the users and in the documentation.
Proposed technical implementation details (optional)
We have update the docs to explain that the parameters are not implemented.
The code should be changed. The parameters should be moved out of the base class and into the cmdlet class GetAuthenticodeSignatureCommand. That way, the parameters only apply to that cmdlet.
See related Docs issue https://github.com/MicrosoftDocs/PowerShell-Docs/issues/7564.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I agree that it would be a breaking change. But I think it falls into the category of minimal risk and impact, since it was never implemented. We take changes like that all the time. Ultimately, it’s the committee’s decision.
@sdwheeler Even if a parameter does nothing, removing a parameter from a cmdlet is a breaking change.