When in a remote workspace or when using Codespaces, Workspace Extensions run on the remote machine / environment.
When in a local workspace, Workspace Extensions run on the local machine. Workspace Extensions: These extensions are run on the same machine as where the workspace is located.
Example UI Extensions include: themes, snippets, language grammars, and keymaps. UI Extensions cannot directly access files in the remote workspace, or run scripts/tools installed in that workspace or on the machine. UI Extensions: These extensions contribute to the VS Code user interface and are always run on the user's local machine. In order to make working with Remote Development or Codespaces as transparent as possible to users, VS Code distinguishes two kinds of extensions: This article summarizes what extension authors need to know about Remote Development and Codespaces including the extension architecture, how to debug your extension in remote workspaces or Codespaces, and recommendations on what to do if your extension does not work properly. While many extensions will work without any modifications, you may need to make changes so that your extension works properly in all environments, although these changes are often fairly minor. However, this can have subtle impacts on how extensions need to work.
To ensure performance, Remote Development and GitHub Codespaces both transparently run certain VS Code extensions remotely. GitHub Codespaces is a service that expands these capabilities with managed cloud-hosted environments that are accessible from both VS Code and a browser-based editor. Visual Studio Code Remote Development allows you to transparently interact with source code and runtime environments sitting on other machines (whether virtual or physical). Edit Supporting Remote Development and GitHub Codespaces
0 kommentar(er)
