Eric Loveland

My feedback

  1. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    The issues you have encountered can be frustrating, sorry that is the case for you.

    Moving this to Survey to try to gauge the scope of the problem for users generally.

    We are somewhat limited by security requirements: what ships with Windows will always be tagged so that nothing can replace it easily unless it is signed by Microsoft. While Pester is part of Windows, it is not owned or developed by Microsoft, so updates delivered via the Gallery cannot be Microsoft signed.

    Once the Gallery version is installed on a system, -SkipPublisherCheck is no longer required for future updates. That first experience, however, is bad.

    This leaves us with a dilemma: do we stop shipping Pester in with PowerShell in the future, or do we continue to provide the feature set knowing users who update from the Gallery will encounter these issues?

    Looking for feedback from as many users…

    Eric Loveland supported this idea  · 
    Eric Loveland commented  · 

    I think @DarwinJS's idea 1 is most feasible based on @J. Keith Bankston [MSFT]'s feedback. I think it would likely require an additional parameter to Uninstall-Module indicating that we're only intending to uninstall a shipped module, so as to avoid version conflicts if we want to reinstall the same version from the gallery for easier future upgrades.

Feedback and Knowledge Base