-
Notifications
You must be signed in to change notification settings - Fork 511
Profiles not loading in lastest preview #3650
New issue
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
Comments
Just FYI for anyone coming to this issue: we discovered it as we were testing the preview release. We decided that hey, it's preview anyway, and our plan was to get this out by the end of October. Since we weren't going to do another release tomorrow (seeing as it's a Friday, and @rjmholt's last day at Microsoft), and come Monday it'll be November, we released regardless. The Preview will, of course have bugs seeing as it contains an entire rewrite of the pipeline execution model and, indeed, PowerShell Editor Services' architecture as a whole. Please help us find those bugs, squash them, and cover them with regression tests! |
not sure if it's related to that exact problem, but when I start VSCode Insiders 1.62.0-insider
f961b92f0faec5c68124ab4d89922d38cf6f513d
x64 on Powershell Name Value
---- -----
PSVersion 7.2.0-rc.1
PSEdition Core
GitCommitId 7.2.0-rc.1
OS Microsoft Windows 10.0.19043
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0 with Extension Version ms-vscode.powershell-preview@2021.10.3 he is also not loading the profile and throwing: "The term 'C:\Users\USERPROFILE\OneDrive' is not recognized as a name of a cmdlet, function, script file, or executable program. interestingly it is not "error-colored" The real path should be: So in my case there might be somewhere a problem with whitespaces in the path. |
I found another issue that is related to this problem. The To test it create Write-Host $profile PowerShell Preview 2021.10.3: PowerShell Preview 2021.10.1: C:\Users\Bukem\Documents\WindowsPowerShell\Microsoft.VSCode_profile.ps1 @andschwa Should I make separate issue or this is enough? |
Thanks @kborowinski! Your report is fine there, I'll be looking at this first thing Monday! |
ConsoleHost: Visual Studio Code Host: |
@JustinGrote Just opened PowerShell/PowerShellEditorServices#1607. Want to take a crack at it? 😁 |
@andschwa currently working on the Pester debug thing, I'm pretty close. |
I feel like there are several different bugs in this thread, but for what it's worth, if you keep your Documents in OneDrive and this bug causes them to fail to run, you can load your profile by hand with $profile.PSObject.Properties.Value.Where({ Test-Path $_ }).ForEach({ . $_ }) |
@Jaykul, indeed, there are! |
Ok, I believe I've resolved the issues here except @JustinGrote's note of the lack of |
And I'm not sure about whitespace 🤷 |
This issue has been marked as fixed. It has been automatically closed for housekeeping purposes. |
Can everyone please test again with |
The 'whitespace one' is also fixed. 😎 |
Works like a charm! |
Prerequisites
Summary
I've defined functionality in my
$profile
but it isn't run at startup.I have to work around it with
. $profile
.PowerShell Version
Visual Studio Code Version
Extension Version
[email protected]
Steps to Reproduce
Put code in profile
Start PowerShell extension
Visuals
Logs
The text was updated successfully, but these errors were encountered: