#Visual studio code how to

Note: You can learn how to get up-and-running quickly with dev containers in the introductory Dev Containers tutorial. You can learn more in our dev container FAQ and on the specification's site v. Note: The Dev Containers extension supports the open Dev Containers Specification, which empowers anyone in any tool to configure a consistent dev environment.

You can attach to a running container to inspect it.

You can use a container as your full-time development environment.

The Dev Containers extension supports two primary operating models: This lets VS Code provide a local-quality development experience including full IntelliSense (completions), code navigation, and debugging regardless of where your tools (or code) are located. This means that you can seamlessly switch your entire development environment just by connecting to a different container. Extensions are installed and run inside the container, where they have full access to the tools, platform, and file system. Workspace files are mounted from the local file system or copied or cloned into the container. This container can be used to run an application or to separate tools, libraries, or runtimes needed for working with a codebase. A devcontainer.json file in your project tells VS Code how to access (or create) a development container with a well-defined tool and runtime stack.

It allows you to open any folder inside (or mounted into) a container and take advantage of Visual Studio Code's full feature set. The Visual Studio Code Dev Containers extension lets you use a container as a full-featured development environment. Configure IntelliSense for cross-compiling.