You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PowerShell Integrated Console is not my default terminal. In a multi-root project, when opening a .ps1 file, the integrated console launches automatically. This is useful since often I'll want to F5 / F8 bits of that file. Sadly however, the working directory of the integrated console is not set to the root folder of the file that induced the launch. If the .ps1 file I'm using is using resources at a relative location and doesn't otherwise handle for the different working directory, this becomes inconvenient. Surely though, it is better to launch the console to the working directory of the file that caused the launch.
Thanks @petervandivier we are currently tracking this request (support for multiple workspaces) with issue #2153 so I will mark this as a duplicate--thanks!
Issue Description
The PowerShell Integrated Console is not my default terminal. In a multi-root project, when opening a .ps1 file, the integrated console launches automatically. This is useful since often I'll want to F5 / F8 bits of that file. Sadly however, the working directory of the integrated console is not set to the root folder of the file that induced the launch. If the .ps1 file I'm using is using resources at a relative location and doesn't otherwise handle for the different working directory, this becomes inconvenient. Surely though, it is better to launch the console to the working directory of the file that caused the launch.
Repro
When clicking on the file
bar.ps1
to open it, you will note that opens to the "baz" working directory.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: