Jesse Silverman

My feedback

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

    We’ll send you updates on this idea

    7 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Jesse Silverman supported this idea  · 
  2. 30 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Jesse Silverman supported this idea  · 
  3. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Jesse Silverman supported this idea  · 
  4. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Jesse Silverman supported this idea  · 
  5. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Jesse Silverman supported this idea  · 
  6. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Jesse Silverman supported this idea  · 
  7. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jesse Silverman commented  · 

    This has been the case for a very long time, it is frustrating only because one of the first exercises in some of the popular PowerShell tutorials and books is to "run Update-Help and ensure that it completes without errors." Then go to a round room and stand in the corner. It does not prevent all of the other help from updating, which would make it a more serious bug.

    However, the error messages you show are outright lies -- "English-US help content is available and can be installed using: Update-Help -UICulture en-US."

    That is intended to show when a specific help item just hasn't been translated to/provided for the UICulture your session is running as, but it still appears when the culture you were going for was en-US in the first place, as you show. That is a separate issue from the fact that the specific help features in question don't have valid content (or at least not valid URL's to the content if they do exist somewhere).

  8. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jesse Silverman commented  · 

    I'm just getting back into PowerShell again for real after some time away, but the approach of adding a separate functionality for -ComputerName for each different command individually was abandoned long ago. Even in 5.1, which I still use sometimes, the "new" way of calling Invoke-Command works just great -- better and more efficiently than calling the Get-Service, Get-Process, etc. etc. commands with the -ComputerName parameter.

    It is a breaking change if you have the commands hard-coded with -ComputerName, i.e. you will need to update your scripts, but from everything I've read it is better to do it with PowerShell remoting and the Invoke-Command -- for one thing, Invoke-Command calls them in parallel, which the built-in -ComputerName in Get-Service, Get-Process etc. did not. There are a few other differences besides that in terms of exactly how the output comes back, but this is squarely the new way going forward, I believe.

Feedback and Knowledge Base