Agreed. At the same time, the ability to package scripts with new minor PS version allows for overcoming the limitation of system-wide PS. Right now, it's possible to have PS LTS as system-wide and for every new script/solution, the sysadmin can choose to package script as 'standalone'.Microsoft’s release cycle is not supportable at this time. ... We also seriously doubt that any corporation or government entity will update its entire network to a new PowerShell version every month. Please let us know in the comments what your position on this is.
Could you decouple this special PS Redistributable into separate 'component' in order to update it with new PS version? So you products can use newly provided "PS Redistributable" without need to update itself?... a runtime installer can be found in the “Redistributable” folder. All PowerShell 7 applications packaged with this build will look for this runtime first before checking on a PowerShell 7 install folder.
This is very nice idea. Deploying packaged script/app will not alter system-wide PowerShell. I cannot stress enought how great this feature is.You can even deploy your PowerShell 7 applications with this runtime to computers that do not have PowerShell 7 installed at all.
But right now, users of PS-based GUI apps need to do following:
1.download and install "PS Redistributable Package"
2.download and extract zip file with "PS-based GUI" application
So how about one step further, for fully-flaged PowerShell Forms application:
Instead of downloading and installing "PS Redistributable Package", would it be possible to take the content of the "PS Redistributable Package" and put it directly (or with extra folder like "pwsh") into the folder with packaged app, as post-compile step? Then, the only thing which user needs to do is to extract zip file with application and that's it. Possible?