Use a container as your full-time environment - Open an existing folder in a container for use as your full-time development environment in few easy steps. When I opened the folder from the command, I spotted the following error in the debug console: No file system provider found for resource. Works with both container and non-container deployed projects. At one point I had a similar command to instantly open a folder in VS Code (Visual Studio Code), but deleted it after I switched from VS Code to Atom. Attach to a running container - Attach to a running container for quick edits, debugging, and triaging. Installing VS Code on MacOS is extremely easy. While searching through the VS Code issues and documentation, I found the following information on opening VS Code with URLs. just find the location that you need to download it to, which normally will be in your Downloads folder. This documentation led me to the solution of opening Windows-based folder paths. To open a project folder, VS Code requires the following URL format: vscode://file// - example: vscode://file/c:/myProject/. Whenever I parsed the above Windows path, I received the following path: C:/data/vscode/test-project-folder. The scheme for this URI is C, which is something VS Code its file system provider does not understand. Looking to the documentation, this should be file. When checking this for a macOS path like /data/vscode/test-project-folder, the scheme is set to file. Instead of using the () method, I tried out the () method for the Windows path and it resulted in: file:///c:/data/vscode/test-project-folder. Using this URI with the vscode.openFolder command did the trick.
0 Comments
Leave a Reply. |