You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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?
Activity
bergmeister commentedon Jan 4, 2018
As discussed in the referenced PR, the new property
ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELLwill only be present in PS 6.1 but it still makes sense to have a general documentation of the current msiTo install PowerShell quietly from command line an eleavted command shell needs to be launched.
One can install PowerShell Core in cmd as follows:
Or in PowerShell as:
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.)
For debugging installer problems, it is also handy to add the following argument, which will create a log file.
bergmeister commentedon Jan 7, 2018
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?
bergmeister commentedon Feb 28, 2018
The referenced PR above added the
ENABLE_PSREMOTINGandREGISTER_MANIFESTproperties that need to be set to 1 in order to be run.SteveL-MSFT commentedon Mar 6, 2018
Sean Wheeler (@sdwheeler) I think we should consider having the installation docs converted to an about_ topic
joeyaiello commentedon Oct 31, 2018
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.
joeyaiello commentedon Oct 31, 2018
Also related to #3048
Syncing from original (#1)