Skip to content

DEVPATH environment variable not being set for interactive console session #532

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.

Sign up for GitHub

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

Jump to bottom
Closed
daviwil opened this issue Mar 14, 2017 · 0 comments
Closed

DEVPATH environment variable not being set for interactive console session #532

daviwil opened this issue Mar 14, 2017 · 0 comments
Assignees
@daviwil
Labels
Issue-Bug A bug to squash.
Milestone
0.10.1

Comments

@daviwil
Copy link
Contributor

daviwil commented Mar 14, 2017

When the powershell.developer.powerShellExeIsWindowsDevBuild setting is used, a DEVPATH environment variable needs to be set on the powershell.exe process that we launch. Currently there's no vscode.createTerminal parameter for setting environment variables so we may need a .bat script to encapsulate that in the short term.
@daviwil daviwil added the Issue-Bug A bug to squash. label Mar 14, 2017
@daviwil daviwil added this to the 0.10.1 milestone Mar 14, 2017
@daviwil daviwil self-assigned this Mar 14, 2017
daviwil added a commit that referenced this issue Mar 16, 2017
@daviwil
Merge pull request #570 from daviwil/fix-532
24c48b7 
Fix #532: DEVPATH env variable not being set for integrated console
@terrorizer1980 terrorizer1980 mentioned this issue Jun 20, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daviwil daviwil

Labels
Issue-Bug A bug to squash.
Projects
None yet
Milestone
0.10.1
Development

No branches or pull requests
1 participant
@daviwil