J. Keith Bankston [MSFT]AdminJ. Keith Bankston [MSFT] (Admin, Windows Server)

My feedback

  1. 1 vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      4 comments  ·  PowerShell » PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
      J. Keith Bankston [MSFT]AdminJ. Keith Bankston [MSFT] (Admin, Windows Server) commented  · 

      Thanks for the updated info. This appears to be fixed (or at least does not repro) with the latest version of PowerShellGet. Please update the powershellget version you have by doing the following:

      > Install-Module PowerShellGet
      > Install-PackageProvider -Name PowerShellGet

      After running this, restart PowerShell and retry the publishing (since the loaded version of the provider will be what was in place before running install-packageprovider).

      So that you know, for my repro case
      1. The difference in what you have installed versus my system is that my version of the PowerShellGet provider is 1.1.2.0.
      2. I made a local copy of your PS1 file, ran test-fileinfo on it, then used publish-script targeting a repo I have set up to a local fileshare.

      If you install 1.1.2.0, and still have this issue, please update this post.

    • 4 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

        survey  ·  0 comments  ·  PowerShell » PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
        J. Keith Bankston [MSFT]AdminJ. Keith Bankston [MSFT] (Admin, Windows Server) supported this idea  · 
      • 1 vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

          5 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →

          Either I’m unable to repro this, or I am missing the issue. I get consistent output between the ISE and standard PS shell.

          Can you provide the following, please, so I can understand it better:
          > Copy & paste the output of the standard shell & the ISE for this command. Don’t worry that it doesn’t look right in this editor, I’ll convert it to a non-proportional font to understand it.
          > In one of the windows, run $psversiontable, and include that in the output.

          One last request – can you try replacing Get-WMIObject with Get-CimInstance & see if it does the same thing? The -WMI cmdlets have been replaced with the largely equivalent -Cim cmdlets for a while, and you should really be using the newer cmdlets.

          J. Keith Bankston [MSFT]AdminJ. Keith Bankston [MSFT] (Admin, Windows Server) commented  · 

          Hi Fred - turns out this is harder to understand using the text output this way. Please contact me using keithb@microsoft.com, if you are willing.
          The one thing I can see - the elipsis in the output from ISE indicates that the screen width for the ISE window prevented you from displaying the same output. Can you confirm that the command add-on window is closed, and that the width of the 2 output display areas (the standard PS prompt and the output window in the ISE) match? Alternatively, it may be easier to set the font temporarily to a smaller size in both views, so that the same number of columns can be displayed.
          If you can, do a screen capture & send me the jpgs using the email address above. I'll respond to you offline. Thank you.

        • 1 vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            survey  ·  3 comments  ·  PowerShell » WinRM  ·  Flag idea as inappropriate…  ·  Admin →
            J. Keith Bankston [MSFT]AdminJ. Keith Bankston [MSFT] (Admin, Windows Server) commented  · 

            I would like to re-name this item to focus on the request for a way to determine if servicing is underway. This seems like it could be achievable, & I would mark it as a Survey item to gauge interest.

            The recommendation to block WinRM during servicing would result in some very bad behaviors, particularly during a rollback. That particular request would have to be declined.

            If this is OK, pls reply or simply modify the title.

          • 7 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

              survey  ·  5 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
              J. Keith Bankston [MSFT]AdminJ. Keith Bankston [MSFT] (Admin, Windows Server) commented  · 

              As an FYI (not disagreeing with the feedback, just providing information) what this command does today is to always place all the required modules in the same path you save the script to. It won't install the modules, but does do a save, as per Save-Module.
              Awaiting feedback from others on this item.

            • 14 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)

                We’ll send you updates on this idea

                6 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →

                Balancing what is in Windows and what is in the Gallery is hard. It would help us to understand why having this in the OS is so much better than having it in the Gallery.

                What would help is to understand why installing the Posh-SYSLOG module from the Gallery is not meeting the need. Merging things into the Windows OS has some big implications, so we are trying to strike the balance. Additional information will help.

              • 28 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  2 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                  J. Keith Bankston [MSFT]AdminJ. Keith Bankston [MSFT] (Admin, Windows Server) commented  · 

                  Moving under the PowerShell area

                • 41 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    planned  ·  13 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                    J. Keith Bankston [MSFT]AdminJ. Keith Bankston [MSFT] (Admin, Windows Server) commented  · 

                    Thanks for filing this. It seems related to this item: https://windowsserver.uservoice.com/admin/forums/301869-powershell/suggestions/11678499-register-psrepository-fails-against-authenticated, which we are also taking a look at.

                  Feedback and Knowledge Base