PSCommunityCall May 21st, 2020
SteveL-MSFT opened this issue · 4 comments
Please add topics and/or questions here.
Agenda:
- Latest PS 7.1 preview
- PSGet 3.0 preview
- Secret Management preview
Please add any topics/questions you want discussed during the call.
The "this ICS file" link in https://github.com/PowerShell/PowerShell-RFC/tree/master/CommunityCall is set from 2019-04-12 and repeat 13 times so if like me you didn't change it when importing there are no more notifications. Probably be good to update the file with repeat from now to ∞
how about update-powershell cmdlet ;)
Honestly the state of the VSCode extension is so frustrating, I rather have a more stable and better preforming extension then having any new features.
There is no point developing new things if the advance and rich IDE turn into Notepad after 5 minutes of use.
I know that many fixes for this problem was released over the years but every the it's coming back and getting even worst.
PowerShell/vscode-powershell#2627
(Sorry for venting some frustration)
@SteveL-MSFT @joeyaiello it's common practice for PATH-type variables to utilise %tokens% to reference other variables.
It works in many cases as long as the OS is handling it. It does not work correctly with .NET's actual Environment.SetEnvironmentVariable API as it messes up the registry format (uses non-expandable registry string type), there's an open issue the .NET team haven't updated in months illustrating that.
Provided that PSModulePath / $PSHOME refers to the environment variable or queries from the env var %programfiles% it will be able to resolve the path correctly I'd imagine even if it's installed to a customized program files path. Just don't try to set an environment variable with [environment]::SetEnvironmentVariable() if it contains tokens intended to be expanded like that.
EDIT: See the .NET issue here: dotnet/runtime#1442