Skip to content

Document PSCore6 MSI properties #2007

Description

@SteveL-MSFT

Issue Details

Christoph Bergmeister (@bergmeister) added new capability to the MSI installer for adding context menus. Users can specify this property with a /q quiet install but needs to know the property name a priori.

Should also document other aspects of the installer like it adds pwsh to the system path.

Version(s) of document impacted

  • Impacts 6 document
  • Impacts 5.1 document
  • Impacts 5.0 document
  • Impacts 4.0 document
  • Impacts 3.0 document

Reason(s) for not selecting all version of documents

  • The documented feature was introduced in selected version of PowerShell
  • This issue only shows up in selected version of the document

Activity

  1. bergmeister commented on Jan 4, 2018

    @bergmeister
    Contributor

    As discussed in the referenced PR, the new property ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL will only be present in PS 6.1 but it still makes sense to have a general documentation of the current msi
    To install PowerShell quietly from command line an eleavted command shell needs to be launched.
    One can install PowerShell Core in cmd as follows:

    msiexec /i Path/To/PowerShell-X.Y.Z.0-x64.msi /q
    

    Or in PowerShell as:

     & Path/To/PowerShell-X.Y.Z.0-x64.msi /q
    

    To check success, one can assert against the exitcode $LASTEXITCODE, which should be 0 .
    In both cases, one can add the following argument to add the context menu to explorer (the value does not need to be one but supplying any value will work.)

     ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1
    

    For debugging installer problems, it is also handy to add the following argument, which will create a log file.

    /l*vx installerLog.txt
    
  2. bergmeister commented on Jan 7, 2018

    @bergmeister
    Contributor

    I see that a lot of installation documentation is in the PowerShell repo (e.g. here). Do we plan to move it to this repo or is the idea to point it to the release specific branch?

  3. bergmeister commented on Feb 28, 2018

    @bergmeister
    Contributor

    The referenced PR above added the ENABLE_PSREMOTING and REGISTER_MANIFEST properties that need to be set to 1 in order to be run.

  4. SteveL-MSFT commented on Mar 6, 2018

    @SteveL-MSFT
    ContributorAuthor

    Sean Wheeler (@sdwheeler) I think we should consider having the installation docs converted to an about_ topic

  5. joeyaiello commented on Oct 31, 2018

    @joeyaiello
    Contributor

    About_topics need to be reconciled all up with the existing TOC. Let's not mix that effort with the need to write content right now.

  6. joeyaiello commented on Oct 31, 2018

    @joeyaiello
    Contributor

    Also related to #3048

  7. added a commit that references this issue on Aug 26, 2019
    0ac3ae8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Pri0Priority - Highestarea-setupArea - Installer packages and configuration

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions