Repository navigation
PowerShell cmdlet(similar to packagemanagement) for Upgrading pwsh #6080
Description
Steve Lee (@SteveL-MSFT) : Just had a though, Why can't we have a PowerShell cmdlet (Update-PowerShell) which will update pwsh to the latest available release.
Activity
[-]PowerShell cmdlet for Upgrading pwsh similar to packagemanagement[/-][+]PowerShell cmdlet(similar to packagemanagement) for Upgrading pwsh [/+]SteveL-MSFT commentedon Jan 31, 2018
Can't find the issue, but we had discussed this previously. Where we landed is that it would be ideal to have a PackageManagement Provider so that you can run
install-package powershelland get the latest version. It's simply a priority and resource problem. It seems ok to update via the msi on Windows and on Linux we already support updates via apt/yum and on macOS it's published to HomeBrew.SwarfegaGit commentedon Feb 1, 2018
On the topic of updating. One annoyance on Windows is that each time I upgrade I have to repin PowerShell to my Start Menu and Taskbar. This is caused by the fact the default installation path includes the version number. E.G...
etc
kvprasoon commentedon Feb 1, 2018
My vote for the above issue
SteveL-MSFT commentedon Feb 1, 2018
Andrew Palmer (@SwarfegaGit) can you open a new issue for that?
iSazonov commentedon Feb 2, 2018
Related comment about the default installation path.
doctordns commentedon Jan 17, 2019
As noted in my issue post - this should just be simpler. I should not have to go to GitHub, select the correct file out of a bunch, download it, then run it and re-pin all the shortcuts.
For developers, this workflow may be great - but you can make a lot simpler.
I'd like a fully supported, in the box Update-PowerShell cmdlet.
iSazonov commentedon Jan 17, 2019
Feel free to discuss in #8663