Justin Grote
Justin Grote
@salsop regardless vmseries1 isn't visible and cannot be added for private marketplace so my vendors who I can't convince to update their templates because it "messes with their process" are...
@goldcode this doesn't work if the assembly is native to pwsh, e.g. 'System.Runtime.CompilerServices.Unsafe', it's only if you have two modules that need different version DLLs. Even then it's a "first...
@hbuckle I can't comment on the "Right" way but what I would envision as a design: 1. Each module gets its own optional loadcontext, a "runspace" of sorts to load...
It seems to me that if a host could declare or be constructed what formats it supports (plaintext only, console emits, ANSI support), then Powershell should send that output to...
> Also just to make sure before I waste any time, @JustinGrote are you or someone else working on this already? Nope I am not, this would be very welcome!
For those who came here from the MSFT documentation like I did, here's a script to automate the process on Windows. https://gist.github.com/JustinGrote/72d7baaa6cc99691b7c4cb3caad54891
It's documented in the source code 👍 It basically tells Powershell to do Remoting protocol xml to stdin/out
It was a joke but it's in the github.com/powershell/powershell repository.
Prompted to update Powershell to non-LTS version even when $Env:POWERSHELL_UPDATECHECK is set to LTS
@Liturgist 7.2 is an LTS version, unless I'm missing something, this is as-expected. If it prompts you for 7.3.x when that chain starts, then there is a problem. Also it's...
Prompted to update Powershell to non-LTS version even when $Env:POWERSHELL_UPDATECHECK is set to LTS
@andschwa so I agree the end-behavior (confirmed by tests) should be as such: 1. If you are on an LTS, do not prompt to update your LTS until it is...