Jaap Brasser

My feedback

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

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    Jaap Brasser commented  · 

    I verified that this is no longer an issue on later builds of Windows 10, here is my output:

    PS C:\Users\JaapBrasser> Install-Script -Name Test-RPC -Scope CurrentUser

    PATH Environment Variable Change
    Your system has not been configured with a default script installation path yet, which means you can only run a script
    by specifying the full path to the script file. This action places the script into the folder
    'C:\Users\JaapBrasser\Documents\WindowsPowerShell\Scripts', and adds that folder to your PATH environment variable. Do
    you want to add the script installation path 'C:\Users\JaapBrasser\Documents\WindowsPowerShell\Scripts' to the PATH
    environment variable?
    [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
    PS C:\Users\JaapBrasser> $PSVersionTable

    Name Value
    ---- -----
    PSVersion 5.1.14342.1000
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    CLRVersion 4.0.30319.42000
    BuildVersion 10.0.14342.1000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

  2. 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 » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Jaap Brasser shared this idea  · 
  3. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  PowerShell » PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
    Jaap Brasser shared this idea  · 

Feedback and Knowledge Base