multi-pwsh 0.7.0 is out with initial #PowerShell virtual environment (venv) support, through runtime hooking of PowerShell, PowerShellGet and PSResourceGet! Try it out now, let me know what you think đŸ‘‡ github.com/Devolutions/...

@awakecoding.com Are we supposed to use multi-pwsh to install #PowerShell on normal workstations?

If yes, it it supposed to do anything with existing installations?

I basically just run https://gist.github.com/sassdawe/49e08d0e4893a5c680e1c7f7e734cb23 in an admin Windows PowerShell every time there is an update to be installed on most of my machines.

But recently I started to test deploying the LTS version with #PatchMyPC

Also, is it expected for #WindowsTerminal to pick up these versions and make them a profile automatically?

Get the latest LTS version of PowerShell

Get the latest LTS version of PowerShell. GitHub Gist: instantly share code, notes, and snippets.

Gist
@sassdawe @awakecoding.com for now multi-pwsh is more like a tool to make user-local installations. I'm trying to make it as flexible as possible such that it could wrap system-wide installations, but I don't intend to make it wrap the MSI installation process at this point. in other words, I could wrap your MSI-based installation, but I wouldn't really wish to bootstrap the MSI installation from multi-pwsh - there's no way to install multiple MSIs side-by-side
@awakecoding @awakecoding.com right! And I'll probably not move forward with MSI based deployment myself but return to the system level zip based installation.
@sassdawe @awakecoding.com I hadn't realized you're literally doing a custom system-wide installation from the zip file. Why not use the MSI? Do you need to have multiple versions of powershell usable for all users? I could improve multi-pwsh to better support zip-based installations for all users, if that's what you're looking for.

@awakecoding @awakecoding.com I used to have all three releases placed side by side system-wide but most recently only one LTS version is installed, but soon I can have two LTS installed again.

And system-wide because I separate admin account from normal user account, plus Intune remediation script are using #pwsh inside Windows #PowerShell