We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PSModulePath is modified with every edit to a file.
Run this in the PSIC:
$env:PSModulePath $env:PSModulePath = "C:\Users\tyleonha\.vscode-insiders\extensions\ms-vscode.powershell-preview-2019.5.0\modules" $env:PSModulePath
Verify it changed.
Now make a single edit to a script and check the PSModulePath once more... It should look like:
C:\Users\tyleonha\Documents\PowerShell\Modules;C:\Users\tyleonha.vscode-insiders\extensions\ms-vscode.powershell-preview-2019.5.0\modules;C:\Program Files\PowerShell\Modules;c:\program files\powershell\7-preview\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules
Apparently, the PSModulePath is updated every time you spin up a Runspace so I wonder if we're doing something like that...
Follow the instructions in the README about capturing and sending logs.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue Description
PSModulePath is modified with every edit to a file.
Steps to repo
Run this in the PSIC:
Verify it changed.
Now make a single edit to a script and check the PSModulePath once more... It should look like:
Apparently, the PSModulePath is updated every time you spin up a Runspace so I wonder if we're doing something like that...
Attached Logs
Follow the instructions in the README about
capturing and sending logs.
Environment Information
Visual Studio Code
PowerShell Information
Visual Studio Code Extensions
Visual Studio Code Extensions(Click to Expand)
The text was updated successfully, but these errors were encountered: